summaryrefslogtreecommitdiff
path: root/rules
AgeCommit message (Collapse)Author
2013-10-16rules: don't limit some of the rules to the "add" actionLennart Poettering
Devices should show up in systemd regardless whether the user invoked "udevadm trigger" or not. Before this change some devices might have suddenly disappeared due issuing that command.
2013-10-16rules: expose loop block devices to systemdLennart Poettering
Since the kernel no longer exposes a large number of "dead" loop devices it is OK to expose them now in systemd, so let's do that. This has the benefit that mount dependencies on loop devices start to work.
2013-10-14backlight: include ID_PATH in file names for backlight settingsLennart Poettering
Much like for rfkill devices we should provide some stability regarding enumeration order, hence include the stable bits of the device path in the file name we store settings under.
2013-10-14rfkill: use ID_PATH as identifier for rfkill state filesLennart Poettering
Let's include the stable device path for the rfkill devices in the name of the file we store the rfkill state in, so that we have some stability regarding enumeration order.
2013-10-14rfkill: add new rfkill tool to save/restore rfkill state across rebootsLennart Poettering
This works analogous to the existing backlight and random seed services
2013-10-14backlight: always prefer "firmware"/"platform" backlights over "raw" ↵Lennart Poettering
backlights if we have both for the same device
2013-10-11Add support for saving/restoring keyboard backlightsBastien Nocera
Piggy-backing on the display backlight code, this saves and restores keyboard backlights on supported devices. The detection code matches that of UPower: http://cgit.freedesktop.org/upower/tree/src/up-kbd-backlight.c#n173 https://bugs.freedesktop.org/show_bug.cgi?id=70367 [tomegun: also work for devices named "{smc,samsung,asus}::kbd_backlight"]
2013-08-14backlight: instead of syspath use sysname for identifying backlight devicesLennart Poettering
This makes the description string of the backlight service a bit nicer.
2013-08-14backlight: add minimal tool to save/restore screen brightness across rebootsLennart Poettering
As many laptops don't save/restore screen brightness across reboots, let's do this in systemd with a minimal tool, that restores the brightness as early as possible, and saves it as late as possible. This will cover consoles and graphical logins, but graphical desktops should do their own per-user stuff probably. This only touches firmware brightness controls for now.
2013-08-0180-net-name-slot.rules: only rename network interfaces on ACTION=="add"Harald Hoyer
Otherwise systemd-udevd will rename on "change" and "move" events, resulting in weird renames in combination with biosdevname systemd-udevd[355]: renamed network interface eth0 to em1 systemd-udevd[355]: renamed network interface eth1 to p3p2 systemd-udevd[357]: renamed network interface eth0 to p3p1 systemd-udevd[429]: renamed network interface p3p2 to ens3f1 systemd-udevd[428]: renamed network interface p3p1 to ens3f0 systemd-udevd[426]: renamed network interface em1 to enp63s0 or systemd-udevd[356]: renamed network interface eth0 to em1 systemd-udevd[356]: renamed network interface eth0 to p3p1 systemd-udevd[420]: renamed network interface p3p1 to ens3f0 systemd-udevd[418]: renamed network interface em1 to enp63s0 systemd-udevd[421]: renamed network interface eth1 to p3p1
2013-07-21rules: net, tty description - ask hwdb explicitly for pci dataKay Sievers
2013-07-20rules: drivers - always call kmod, even when a driver is bound to the deviceKay Sievers
On Sat, Jul 20, 2013 at 12:56 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > After a recent change present in 3.11-rc1 there is a driver, called processor, > that can be bound to the CPU devices whose sysfs directories are located under > /sys/devices/system/cpu/. A side effect of this is that, after the driver has > been bound to those devices, the kernel adds DRIVER=processor to ENV for CPU > uevents and they don't match the default rule for autoloading modules matching > MODALIAS: > > DRIVER!="?*", ENV{MODALIAS}=="?*", IMPORT{builtin}="kmod load $env{MODALIAS}" > > any more. However, there are some modules whose module aliases match specific > CPU features through the modalias string and those modules should be loaded > automatically if a compatible CPU is present. Yet, with the processor driver > bound to the CPU devices the above rule is not sufficient for that, so we need > a new default udev rule allowing those modules to be autoloaded even if the > CPU devices have drivers.
2013-07-18rules: keyboard - use builtin commandKay Sievers
2013-07-10udev: add builtin 'keyboard' to manage key mappingsKay Sievers
2013-06-17rules: only run systemd-sysctl when a network device is addedRoss Lagerwall
Otherwise, when a network device is renamed, systemd-sysctl is run twice with the same network device name: once for ACTION="add" and once for ACTION="move".
2013-04-26always unconditionally create /dev/rtc and use it internallyKay Sievers
Partially revert 2b3c81b02fa5dd47b19558c7684e113f36a48486, which tried to avoid inconsistent rules about when and how to create the /dev/rtc symlink. Instead of conditionally or not creating the /dev/rtc link at all, now always create it with additional and more reliable udev rules. First try to find the "system rtc" with the hctosys flag, if this is not found, fall back to create the link for /dev/rtc0. Our code now never actively searches for the "system rtc" it can always use /dev/rtc.
2013-04-24do not create /dev/rtc symlink, let systemd search for it if neededKay Sievers
The export of the RTCs hctosys flag is uneccesary, the kernel takes care of the persistemt clock management itself, without any need for: CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" "Chaotic hardware platforms" without native kernel persistent clock support will find the proper RTC with the logic rtc_open() without the need for a custom symlink.
2013-03-22Drop trailing whitespaceTollef Fog Heen
2013-03-20rules: move builtin calls before the permissions sectionKay Sievers
<heftig> kay: systemd commit 22582bb broke cups usb printing for me <heftig> because the "lp" group isn't applied anymore <heftig> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", GROUP="lp" <heftig> moving this line to the end of 50-udev-default.rules restores correct behavior, as it's after usb_id
2013-03-18udev: rename kernel command line option to net.ifnames=Kay Sievers
2013-03-18udev: builtin - use RUN rather than IMPORT for loading modulesTom Gundersen
The 'kmod' builtin, like the 'firmware' and 'uaccess' builtins, does not set any variables, so don't use IMPORT. Notice that this changes the behaviour slightly: the processing of subsequent rules for the event that loads a module will no longer wait for the module loading to finish. This is not expected to cause any problems, but we should keep an eye on it.
2013-03-18udev: net-name-slot - disable by kernel command line switchTom Gundersen
The properties will still be set in the udev database, but they will not be used for setting the interface names. As for the other kernel commandline switches, we allow it to be prefixed by 'rd.' to only apply in the initrd.
2013-03-18udev: make firmware loading optional and disable by defaultTom Gundersen
Distros that whish to support old kernels should set --with-firmware-dirs="/usr/lib/firmware/updates:/usr/lib/firmware" to retain the old behaviour.
2013-01-28rules: there is no "ata" subsystem for ATA deviceKay Sievers
2013-01-27udev: set default rules permissions only at "add" eventsKay Sievers
2013-01-06udev: fix net name rules matchesKay Sievers
2013-01-06udev: enable persistent network device namingKay Sievers
2012-12-06rules: usb-hid-pm - remove AMI devicesKay Sievers
On Thu, Dec 6, 2012 at 9:20 AM, Robert Milasan <rmilasan@suse.com> wrote: > It seems that the added rules: > > ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="046b", > ATTR{idProduct}=="ff10", TEST=="power/control", > ATTR{power/control}="auto" > > creates problems for people with Supermicro X8ST3 mb (and maybe > other Supermicro mb's) and renders the KVM-over-IP unusable, at BIOS > and GRUB the KVM works perfectly, but after that the device is unusable. > > Dropping the rule fixes the issue. > > Reference bug: https://bugzilla.novell.com/show_bug.cgi?id=792576
2012-11-20build-sys: make loadable module support optionalTom Gundersen
kmod is unecessary if loadable module support is disabled in the kernel, so make the dependency optional.
2012-11-09udev: net_id - add builtin to retrieve data for network devicesKay Sievers
2012-10-25rules: fix usb_id/hwdb mixup in tty-description.rulesKay Sievers
<grawity> btw, in 15ce372b75a "call 'hwdb' with --subsystem=" you actually added "usb_id --subsystem=usb" (75-tty-description.rules) <kay> ouch :)
2012-10-25rules: call hwdb for all devices with a 'modalias'Kay Sievers
2012-10-25rules: call 'hwdb' with --subsystem= where appropriateKay Sievers
2012-10-23rules: Remove HP iLO from USB HID PM rulesTony Camuso
HP iLO fw versions below 1.50 incorrectly report that HP iLO virtual Kbd/Mouse supports remote wakeup. With the rules change in commit 3bfc7a97b1824fcdfb738617d9a5450a20a22a0f, the HP iLO was listed for power control. In iLO fw versions less than 1.50, the iLO Kbd/Mouse become unresponsive once they are suspended. HP iLO fw versions 1.50+ correctly report that they don't support remote wakeup, which makes the rules moot in any case.
2012-10-23udev: add hardware database supportKay Sievers
2012-10-17timedatectl: introduce new command line client for timedatedLennart Poettering
Much like logind has a client in loginctl, and journald in journalctl introduce timedatectl, to change the system time (incl. RTC), timezones and related settings.
2012-10-11rules: Fix persistent input symlinks for interface 00Martin Pitt
Commits 5e9eb156c and 32567f8 introduced persistent symlinks for input devices with more than one interface. However, this does not ensure stability for the "default" interface, i. e. with interface number 00 or a nonexisting one. If a device with a higher interface number appears first, it'll claim the symlink name without an interface number, and the "interface 00" device won't get any. Fix this by creating the default symlink only for interface 00 or a nonexisting one, so that we properly partition the two cases over the two rules. https://launchpad.net/bugs/1057824
2012-10-09udev: support multiple entries for ENV{SYSTEMD_ALIAS} and ENV{SYSTEM_WANTS}Kay Sievers
2012-09-24rules: only mark MD disks, not partitions, with SYSTEMD_READY=0Kay Sievers
2012-09-17udev: add btrfs supportKay Sievers
All "btrfs" file systems will be registered with the kernel when they show up. Incomplete multi-device volumes will set SYSTEMD_READY=0, to prevent access until the volume is complete and fully registered.
2012-07-3099-systemd.rules.in: ignore nbd in the "add" ueventHarald Hoyer
2012-07-30rules/99-systemd.rules.in: ENV{SYSTEMD_READY}="0" for incomplete mdHarald Hoyer
2012-07-24rules: avoid mounting raid devices too earlyMichal Schmidt
/dev/md0 appears as soon as the first component of the raid array is added by incremental assembly rules. This is too early for systemd to attempt to mount the device. The device should be considered plugged after the raid array becomes active. https://bugzilla.redhat.com/show_bug.cgi?id=767561
2012-07-14rules: fix typo in 42-usb-hid-pm.rulesKay Sievers
<arjan> can you open the 42-usb-hid-pm.rules file <arjan> and go to line 46 <arjan> and tell me why ATTR{idProduct}="0002" only has one = and not two (e.g. == ) ? <kay> arjan: yep <kay> arjan: bug
2012-05-27rules: Limit USB autosuspend on USB HID devicesMatthew Garrett
Some USB ports on external hubs may be reported as "fixed". We only want to auto-enable this on ports that are internal to the machine, so check the parent state as well.
2012-04-15udev: update some rulesKay Sievers
2012-04-14udev: trivial gtk-doc updateKay Sievers
2012-04-14udev: move all unconditionally installed rules to rules/Kay Sievers
2012-04-12getty: VC devices are always available, we don't need to wait until they show upLennart Poettering
2012-04-12relicense to LGPLv2.1 (with exceptions)Lennart Poettering
We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-11-03 09:05:58 +0000