summaryrefslogtreecommitdiffstats
path: root/rules (follow)
Commit message (Collapse)AuthorAgeFilesLines
* getty: Start getty on 3270 terminals available on Linux on System zHendrik Brueckner2014-03-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add the first 3270 terminal device that is associated with the Linux preferred console to the list of virtualization consoles. This is required to automatically start a getty if the conmode=3270 kernel parameter is specified for Linux on z/VM instances. Note that a queued upstream patch also enable the 3270 terminal device if it is associated with the Linux preferred console. How To successfully start agetty on a 3270 terminal, a change in the agetty parameter order is required. Previously, agetty would started like this: /sbin/agetty --keep-baud 3270/tty1 115200,38400,9600 TERM The agetty program interprets the "3270/tty1" as baud rate and fails to start with the "bad speed: 3270/tty1" error message. Fixing this in agetty is more complex rather than reordering the command line parameters like this: /sbin/agetty --keep-baud 115200,38400,9600 3270/tty1 TERM According to agetty sources and "agetty --help", agetty accepts the "tty", "baudrate tty", and "tty baudrate" specifications. P.S. The "tty: Set correct tty name in 'active' sysfs attribute" introduces a change to display the terminal device which is associated with the Linux preferred console. This change helps to let systemd handle this particular case only. Without the changes of this commit, no additional 3270 terminal device can be managed by systemd. https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git/commit/?id=723abd87f6e536f1353c8f64f621520bc29523a3
* gpt-auto-generator: rename root device node symlink to /dev/gpt-auto-rootLennart Poettering2014-03-111-1/+1
| | | | | | Before it was placed in /dev/disk/by-id, which makes it a bit too much API. However, it's mostly an implementation detail for now, hence move it out of the stable block device dir.
* rules: mark loop device as SYSTEMD_READY=0 if no file is attachedPeter Rajnoha2014-03-101-0/+3
| | | | | | Check existence of loop/backing_file in sysfs and mark loop devices with SYSTEMD_READY if missing. Such loop files is uninitialized and it's not ready for use yet (there's no file attached).
* udev: automatically create a symlink /dev/disk/by-id/gpt-auto-root if ↵Lennart Poettering2014-03-071-0/+3
| | | | there's a suitable root partition
* udev/rules: setup tty permissions and group for sclp_line, ttysclp and 3270/ttyLukas Nykryn2014-02-271-0/+3
|
* udev: net_setup - import ID_NET_DRIVERTom Gundersen2014-02-211-0/+2
| | | | This will do until all net properties are imported.
* doc: update punctuationJan Engelhardt2014-02-181-1/+1
| | | | Resolve spotted issues related to missing or extraneous commas, dashes.
* udev: add zram to the list of devices inappropriate for symlinksJóhann B. Guðmundsson2014-02-061-1/+1
| | | | | | udev seems to have a race condition with swapon to see which can open /dev/zram0 first, causing swapon to fail. Seems to be most noticeable on arm devices one out of every 7 times or something.
* s390/getty-generator: initialize essential system terminals/consolesHendrik Brueckner2014-01-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | Ensure to start getty programs on all essential system consoles on Linux on System z. Add these essential devices to the list of virtualization_consoles to always generate getty configurations. For the sake of completion, the list of essential consoles is: /dev/sclp_line0 - Operating system messages applet (LPAR) /dev/ttysclp0 - Integrated ASCII console applet (z/VM and LPAR) /dev/ttyS0 - Already handled by systemd (3215 console on z/VM) /dev/hvc0 - Already handled by systemd (IUCV HVC terminal on z/VM) Depending on the environment, z/VM or LPAR, only a subset of these terminals are available. See also RH BZ 860158[1] "Cannot login via Operating System Console into RHEL7 instance installed on a LPAR". This bugzilla actually blocks the installation of Linux on System z instances in LPAR mode. [1] https://bugzilla.redhat.com/show_bug.cgi?id=860158
* rules: drivers - do not reset RUN listKay Sievers2014-01-031-7/+7
|
* rules: simply 60-drm.rulesDavid Herrmann2013-11-031-6/+1
| | | | We don't need any GOTO, if we merge all matches into a single line.
* rules: load path_id on DRM devicesDavid Herrmann2013-11-031-0/+8
| | | | | | | | | | The path_id-builtin provides useful unique aliases for DRM devices. If we want to configure DRM render-nodes for compositors, we want to avoid storing the whole sys-path in configuration files. Hence, allow users to store the short PATH_ID instead. Load path_id-builtin unconditionally on DRM devices now to always provide this alias.
* udev: link-config - let udevd set the ifnameTom Gundersen2013-10-301-1/+3
|
* udev: builtin - rename net_link to net_setup_linkTom Gundersen2013-10-291-4/+4
| | | | Also add shell completions.
* udev: link-config - move naming policy from udev rulesTom Gundersen2013-10-281-14/+0
| | | | | | | | | | | This introduces a new key NamePolicy, which takes an ordered list of naming policies. The first successful one is applide. If all fail the value of Name (if any) is used. The possible policies are 'onboard', 'slot', 'path' and 'mac'. This patch introduces a default link file, which replaces the equivalent udev rule.
* udev: add network link configuration toolTom Gundersen2013-10-261-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This tool applies hardware specific settings to network devices before they are announced via libudev. Settings that will probably eventually be supported are MTU, Speed, DuplexMode, WakeOnLan, MACAddress, MACAddressPolicy (e.g., 'hardware', 'synthetic' or 'random'), Name and NamePolicy (replacing our current interface naming logic). This patch only introduces support for Description, as a proof of concept. Some of these settings may later be overriden by a network management daemon/script. However, these tools should always listen and wait on libudev before touching a device (listening on netlink is not enough). This is no different from how things used to be, as we always supported changing the network interface name from udev rules, which does not work if someone has already started using it. The tool is configured by .link files in /etc/net/links/ (with the usual overriding logic in /run and /lib). The first (in lexicographical order) matching .link file is applied to a given device, and all others are ignored. The .link files contain a [Match] section with (currently) the keys MACAddress, Driver, Type (see DEVTYPE in udevadm info) and Path (this matches on the stable device path as exposed as ID_PATH, and not the unstable DEVPATH). A .link file matches a given device if all of the specified keys do. Currently the keys are treated as plain strings, but some limited globbing may later be added to the keys where it makes sense. Example: /etc/net/links/50-wireless.link [Match] MACAddress=98:f2:e4:42:c6:92 Path=pci-0000:02:00.0-bcma-0 Type=wlan [Link] Description=The wireless link
* rules: remove pointless MODE= settingsKay Sievers2013-10-211-4/+2
| | | | | | | | | | Changing the default MODE= for the group accessi, but not specifying a GROUP= does not provide anything. It disables the default logic that the mode switches to 0660 as soon as a GROUP= is specifed, which make custom rules uneccesarily complicated. https://bugs.freedesktop.org/show_bug.cgi?id=70665
* rules: don't limit some of the rules to the "add" actionLennart Poettering2013-10-161-5/+5
| | | | | | 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.
* rules: expose loop block devices to systemdLennart Poettering2013-10-161-3/+3
| | | | | | 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.
* backlight: include ID_PATH in file names for backlight settingsLennart Poettering2013-10-141-2/+2
| | | | | | 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.
* rfkill: use ID_PATH as identifier for rfkill state filesLennart Poettering2013-10-141-1/+1
| | | | | | 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.
* rfkill: add new rfkill tool to save/restore rfkill state across rebootsLennart Poettering2013-10-141-0/+4
| | | | This works analogous to the existing backlight and random seed services
* backlight: always prefer "firmware"/"platform" backlights over "raw" ↵Lennart Poettering2013-10-141-4/+4
| | | | backlights if we have both for the same device
* Add support for saving/restoring keyboard backlightsBastien Nocera2013-10-111-1/+3
| | | | | | | | | | | | 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"]
* backlight: instead of syspath use sysname for identifying backlight devicesLennart Poettering2013-08-141-1/+1
| | | | This makes the description string of the backlight service a bit nicer.
* backlight: add minimal tool to save/restore screen brightness across rebootsLennart Poettering2013-08-142-0/+5
| | | | | | | | | | 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.
* 80-net-name-slot.rules: only rename network interfaces on ACTION=="add"Harald Hoyer2013-08-011-1/+1
| | | | | | | | | | | | | | | | | | | | 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
* rules: net, tty description - ask hwdb explicitly for pci dataKay Sievers2013-07-212-4/+3
|
* rules: drivers - always call kmod, even when a driver is bound to the deviceKay Sievers2013-07-201-1/+1
| | | | | | | | | | | | | | | | | | | 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.
* rules: keyboard - use builtin commandKay Sievers2013-07-181-3/+3
|
* udev: add builtin 'keyboard' to manage key mappingsKay Sievers2013-07-101-0/+22
|
* rules: only run systemd-sysctl when a network device is addedRoss Lagerwall2013-06-171-1/+1
| | | | | | 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".
* always unconditionally create /dev/rtc and use it internallyKay Sievers2013-04-261-0/+4
| | | | | | | | | | | | | | | 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.
* do not create /dev/rtc symlink, let systemd search for it if neededKay Sievers2013-04-241-3/+0
| | | | | | | | | | | 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.
* Drop trailing whitespaceTollef Fog Heen2013-03-221-1/+1
|
* rules: move builtin calls before the permissions sectionKay Sievers2013-03-201-6/+9
| | | | | | | <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
* udev: rename kernel command line option to net.ifnames=Kay Sievers2013-03-181-4/+2
|
* udev: builtin - use RUN rather than IMPORT for loading modulesTom Gundersen2013-03-181-6/+6
| | | | | | | | | | 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.
* udev: net-name-slot - disable by kernel command line switchTom Gundersen2013-03-181-0/+5
| | | | | | 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.
* udev: make firmware loading optional and disable by defaultTom Gundersen2013-03-182-1/+3
| | | | | | Distros that whish to support old kernels should set --with-firmware-dirs="/usr/lib/firmware/updates:/usr/lib/firmware" to retain the old behaviour.
* rules: there is no "ata" subsystem for ATA deviceKay Sievers2013-01-281-2/+0
|
* udev: set default rules permissions only at "add" eventsKay Sievers2013-01-271-32/+10
|
* udev: fix net name rules matchesKay Sievers2013-01-061-3/+3
|
* udev: enable persistent network device namingKay Sievers2013-01-061-0/+11
|
* rules: usb-hid-pm - remove AMI devicesKay Sievers2012-12-061-9/+3
| | | | | | | | | | | | | | | | | 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
* build-sys: make loadable module support optionalTom Gundersen2012-11-202-1/+1
| | | | | kmod is unecessary if loadable module support is disabled in the kernel, so make the dependency optional.
* udev: net_id - add builtin to retrieve data for network devicesKay Sievers2012-11-092-8/+6
|
* rules: fix usb_id/hwdb mixup in tty-description.rulesKay Sievers2012-10-251-3/+4
| | | | | | <grawity> btw, in 15ce372b75a "call 'hwdb' with --subsystem=" you actually added "usb_id --subsystem=usb" (75-tty-description.rules) <kay> ouch :)
* rules: call hwdb for all devices with a 'modalias'Kay Sievers2012-10-251-1/+3
|
* rules: call 'hwdb' with --subsystem= where appropriateKay Sievers2012-10-252-2/+2
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-11 16:37:05 +0100