Shea Levy 9bc021ceda Set the firmware_class path in modprobe.d ... Activation scripts are run before systemd is started, so unless users are loading firmware in the initrd (which AFAICT we currently have no support for) the previous /sys-based setting of firmware_class was ineffective on boot. Signed-off-by: Shea Levy <shea@shealevy.com>		2013-04-30 11:46:34 -04:00
..
acpid.nix	Merge remote-tracking branch 'origin/systemd'	2013-01-21 12:45:50 +01:00
bluetooth.nix	bluetooth: add the systemd unit needed for activation by recent bluez versions	2013-02-10 20:30:02 +02:00
nvidia-optimus.nix	nixos support for nvidia optimus	2012-02-06 19:14:42 +00:00
pcscd.nix	strip trailing whitespace; no functional change	2011-09-14 18:20:50 +00:00
pommed.nix	Remove unnecessary (AFAICT) call to toPath	2012-11-15 23:07:05 +01:00
sane.nix	scanner support: create scanner group. Users need to be in this group to access scanners.	2012-12-06 02:59:34 +02:00
thinkfan.nix	add thinkfan service	2013-04-06 23:35:04 +02:00
udev.nix	Set the firmware_class path in modprobe.d	2013-04-30 11:46:34 -04:00
udisks2.nix	udisks2: add udisks2 service	2013-04-04 12:06:34 +04:00
udisks.nix	strip trailing whitespace; no functional change	2011-09-14 18:20:50 +00:00
upower.nix	Rename ‘system.build.systemd’ to ‘systemd.package’	2013-01-16 13:17:57 +01:00