mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-23 18:23:32 +08:00
Code Issues Packages Projects Releases Wiki Activity
f9a6cb0e13
systemd/rules.d/99-systemd.rules.in

83 lines
4.9 KiB
Plaintext
Raw Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 12:23:58 +08:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license headers to various assorted files
2017-11-19 01:18:16 +08:00
#
udev: look for new instead of add action
2010-04-11 03:23:55 +08:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
relicense to LGPLv2.1 (with exceptions) 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.
2012-04-12 06:20:58 +08:00
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
udev: look for new instead of add action
2010-04-11 03:23:55 +08:00
# (at your option) any later version.
udev: install rules file that ignore those nasty useless tty devices by default
2010-04-11 01:18:21 +08:00
udev: simplify udev rules a bit
2011-05-26 08:16:17 +08:00
ACTION=="remove", GOTO="systemd_end"
udev: install rules file that ignore those nasty useless tty devices by default
2010-04-11 01:18:21 +08:00
getty: Start getty on 3270 terminals available on Linux on System z 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
2014-03-12 01:41:09 +08:00
SUBSYSTEM=="tty", KERNEL=="tty[a-zA-Z]*|hvc*|xvc*|hvsi*|ttysclp*|sclp_line*|3270/tty[0-9]*", TAG+="systemd"
udev: tag virtio serial ports with systemd by default
2011-07-06 02:32:08 +08:00
KERNEL=="vport*", TAG+="systemd"
rules: allow systemd to manage UBI volumes (#5214) UBI is a software layer on top of MTD devices that is used with flash chips.
2017-02-03 16:26:50 +08:00
SUBSYSTEM=="ubi", TAG+="systemd"
rules: systemd - remove legacy "ram" from block device blacklist
2015-03-12 23:28:38 +08:00
SUBSYSTEM=="block", TAG+="systemd"
rules: import previous SYSTEMD_READY state for suspended DM devices and skip other rules We can't get any FS meta-data from a suspended device. Hence defer making any plugged/unplugged decisions, i.e. we just import whatever was previous state and skip processing all other rules. Thanks Lennart Poettering <lennart@poettering.net> for suggesting this solution.
2022-08-02 18:38:30 +08:00
# We can't make any conclusions about suspended DM devices so let's just import previous SYSTEMD_READY state and skip other rules
SUBSYSTEM=="block", ENV{DM_SUSPENDED}=="1", IMPORT{db}="SYSTEMD_READY", GOTO="systemd_end"
rules: set SYSTEMD_READY=0 on DM_UDEV_DISABLE_OTHER_RULES_FLAG=1 only with ADD event (#2747) The "SYSTEMD_READY=0" will cause automatic unmount of mountpoint that is on top of such DM device if this is used with multipath which sets DM_UDEV_DISABLE_OTHER_RULES_FLAG in case we have a CHANGE event thatcomes after DM multipath device reload when one of the paths is down or up. See https://bugzilla.redhat.com/show_bug.cgi?id=1312011
2016-04-12 13:44:28 +08:00
SUBSYSTEM=="block", ACTION=="add", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"
udev: don't ignore non-encrypted block devices with no superblock They might be encrypted disks with no LUKS header. https://bugzilla.redhat.com/show_bug.cgi?id=679842
2011-03-01 05:04:53 +08:00
# Ignore encrypted devices with no identified superblock on it, since
# we are probably still calling mke2fs or mkswap on it.
rules: systemd - remove legacy "ram" from block device blacklist
2015-03-12 23:28:38 +08:00
SUBSYSTEM=="block", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_TYPE}=="", ENV{ID_FS_USAGE}=="", ENV{SYSTEMD_READY}="0"
device: allow easy identification of network interfaces without their full sysfs device path
2010-05-10 10:08:53 +08:00
rules: import previous SYSTEMD_READY state for suspended DM devices and skip other rules We can't get any FS meta-data from a suspended device. Hence defer making any plugged/unplugged decisions, i.e. we just import whatever was previous state and skip processing all other rules. Thanks Lennart Poettering <lennart@poettering.net> for suggesting this solution.
2022-08-02 18:38:30 +08:00
# Explicitly set SYSTEMD_READY=1 for DM devices that don't have it set yet, so that we always have something to import above
SUBSYSTEM=="block", ENV{DM_UUID}=="?*", ENV{SYSTEMD_READY}=="", ENV{SYSTEMD_READY}="1"
gpt-auto-generator: support LUKS encrypted root partitions Previously, we supported GPT auto-discovery for /home and /srv, but not for the root partition. Add that, too. Fixes: #859
2016-12-14 01:16:22 +08:00
# add symlink to GPT root disk
SUBSYSTEM=="block", ENV{ID_PART_GPT_AUTO_ROOT}=="1", ENV{ID_FS_TYPE}!="crypto_LUKS", SYMLINK+="gpt-auto-root"
SUBSYSTEM=="block", ENV{ID_PART_GPT_AUTO_ROOT}=="1", ENV{ID_FS_TYPE}=="crypto_LUKS", SYMLINK+="gpt-auto-root-luks"
SUBSYSTEM=="block", ENV{DM_UUID}=="CRYPT-*", ENV{DM_NAME}=="root", SYMLINK+="gpt-auto-root"
rules: avoid mounting raid devices too early /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-24 15:47:33 +08:00
# Ignore raid devices that are not yet assembled and started
rules: only mark MD disks, not partitions, with SYSTEMD_READY=0
2012-09-24 20:55:25 +08:00
SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", TEST!="md/array_state", ENV{SYSTEMD_READY}="0"
SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", ATTR{md/array_state}=="|clear|inactive", ENV{SYSTEMD_READY}="0"
rules: avoid mounting raid devices too early /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-24 15:47:33 +08:00
rules: mark loop device as SYSTEMD_READY=0 if no file is attached 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).
2014-03-11 05:58:14 +08:00
# Ignore loop devices that don't have any file attached
rules: allow systemd to manage loop device partitions SYSTEMD_READY is currently set to 0 for all loop devices (loop[0-9]*) that do not have a backing_file. Partitioned loop devices (ex. loop0p1), however, are matched by this rule and excluded by systemd even though they are active devices. This change adds an additional check to the rule, ensuring that only top level loop devices (loop[0-9]+$) are excluded from systemd.
2014-07-31 23:38:21 +08:00
SUBSYSTEM=="block", KERNEL=="loop[0-9]*", ENV{DEVTYPE}=="disk", TEST!="loop/backing_file", ENV{SYSTEMD_READY}="0"
rules: mark loop device as SYSTEMD_READY=0 if no file is attached 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).
2014-03-11 05:58:14 +08:00
Mark nbd as inactive until connected (#2422) Currently, 99-systemd.rules.in contains a line for network block devices, which mark them as inactive until the first change event, and as active from then on forward. This is not correct. A network block device can be connected or disconnected; this state is signalled by the presence or absense of a "pid" file, which contains the PID of the nbd client userspace process that started the connection. Update the rules file so that it checks for the presence of that file to decide what to set SYSTEMD_READY to. Note that current kernels do issue a change event upon connecting the device, but not yet upon disconnecting. While it's possible to wait until that's been fixed, the behaviour of the rule with TEST!="pid" in the absence of a proper uevent is exactly the same as the behaviour of the old rule; so it should be safe to apply now. Signed-off-by: Wouter Verhelst <w@uter.be>
2016-04-18 22:29:10 +08:00
# Ignore nbd devices until the PID file exists (which signals a connected device)
SUBSYSTEM=="block", KERNEL=="nbd*", ENV{DEVTYPE}=="disk", TEST!="pid", ENV{SYSTEMD_READY}="0"
99-systemd.rules.in: ignore nbd in the "add" uevent
2012-07-31 03:21:37 +08:00
systemadm: consider units with a job live
2010-05-16 08:37:59 +08:00
# We need a hardware independent way to identify network devices. We
rules: systemd - remove legacy "ram" from block device blacklist
2015-03-12 23:28:38 +08:00
# use the /sys/subsystem/ path for this. Kernel "bus" and "class" names
# should be treated as one namespace, like udev handles it. This is mostly
# just an identification string for systemd, so whether the path actually is
device: allow easy identification of network interfaces without their full sysfs device path
2010-05-10 10:08:53 +08:00
# accessible or not does not matter as long as it is unique and in the
# filesystem namespace.
udev: support multiple entries for ENV{SYSTEMD_ALIAS} and ENV{SYSTEM_WANTS}
2012-10-09 06:16:50 +08:00
SUBSYSTEM=="net", KERNEL!="lo", TAG+="systemd", ENV{SYSTEMD_ALIAS}+="/sys/subsystem/net/devices/$name"
udev: merge rules for bluetooth device
2020-09-07 14:06:00 +08:00
SUBSYSTEM=="bluetooth", TAG+="systemd", ENV{SYSTEMD_ALIAS}+="/sys/subsystem/bluetooth/devices/%k", \
ENV{SYSTEMD_WANTS}+="bluetooth.target", ENV{SYSTEMD_USER_WANTS}+="bluetooth.target"
udev: install rules file that ignore those nasty useless tty devices by default
2010-04-11 01:18:21 +08:00
rules: enable hardware-related targets also for user instances > the odd thing is that these units are also defined for the systemd user > instance. However, because these are bound to SYSTEMD_USER_WANTS rather than > SYSTEMD_WANTS they are effectively useless unless some other software > installs the corresponding udev rules first. This adds the rules and starts those targets also for user instances. Fixes #12330.
2019-05-28 20:10:44 +08:00
ENV{ID_SMARTCARD_READER}=="?*", TAG+="systemd", ENV{SYSTEMD_WANTS}+="smartcard.target", ENV{SYSTEMD_USER_WANTS}+="smartcard.target"
udev: Fix sound.target dependency The recent bug report indicated a race at device creation and the sound.target dependencies, and the cause turned out to be the condition of the sound.target trigger. Currently it's set for "card*", but this is actually the parent object; i.e. the sound.target is triggered before the sound devices are created. For assuring the whole sound device creations beforehand, we need to use "controlC*" instead of "card*"; as already described in 78-sound-card.rules, this is guaranteed to be the last device, and can be used as a synchronization point. BugLink: https://bugzilla.suse.com/show_bug.cgi?id=1179363 Signed-off-by: Takashi Iwai <tiwai@suse.de>
2020-12-09 17:56:51 +08:00
SUBSYSTEM=="sound", KERNEL=="controlC*", TAG+="systemd", ENV{SYSTEMD_WANTS}+="sound.target", ENV{SYSTEMD_USER_WANTS}+="sound.target"
units: introduce bluetooth.target/printer.target which are activated if the right hardware is plugged in
2010-07-13 08:16:44 +08:00
rules: enable hardware-related targets also for user instances > the odd thing is that these units are also defined for the systemd user > instance. However, because these are bound to SYSTEMD_USER_WANTS rather than > SYSTEMD_WANTS they are effectively useless unless some other software > installs the corresponding udev rules first. This adds the rules and starts those targets also for user instances. Fixes #12330.
2019-05-28 20:10:44 +08:00
SUBSYSTEM=="printer", TAG+="systemd", ENV{SYSTEMD_WANTS}+="printer.target", ENV{SYSTEMD_USER_WANTS}+="printer.target"
SUBSYSTEM=="usb", KERNEL=="lp*", TAG+="systemd", ENV{SYSTEMD_WANTS}+="printer.target", ENV{SYSTEMD_USER_WANTS}+="printer.target"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="systemd", ENV{SYSTEMD_WANTS}+="printer.target", ENV{SYSTEMD_USER_WANTS}+="printer.target"
udev: pull in printer.target from all kinds of printers
2011-07-05 09:27:14 +08:00
units: add usb-gadget target Linux can be run on a device meant to act as a USB peripheral. In order for a machine to act as such a USB device it has to be equipped with a UDC - USB Device Controller. This patch adds a target reached when UDC becomes available. It can be used for activating e.g. a service unit which composes a USB gadget with configfs and activates it.
2019-01-29 18:13:44 +08:00
SUBSYSTEM=="udc", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}+="usb-gadget.target"
udev: asynchronously mount fuse/confifgs as soon as the kmods are loaded
2011-09-22 09:02:15 +08:00
# Apply sysctl variables to network devices (and only to those) as they appear.
meson: use jinja2 for rules.d templates
2021-05-16 21:51:17 +08:00
ACTION=="add", SUBSYSTEM=="net", KERNEL!="lo", RUN+="{{ROOTLIBEXECDIR}}/systemd-sysctl --prefix=/net/ipv4/conf/$name --prefix=/net/ipv4/neigh/$name --prefix=/net/ipv6/conf/$name --prefix=/net/ipv6/neigh/$name"
sysctl: apply network specific sysctls to each network card as they appear
2011-07-26 02:24:58 +08:00
backlight: always prefer "firmware"/"platform" backlights over "raw" backlights if we have both for the same device
2013-10-14 08:12:52 +08:00
# Pull in backlight save/restore for all backlight devices and
# keyboard backlights
rules: don't limit some of the rules to the "add" action 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-16 08:51:24 +08:00
SUBSYSTEM=="backlight", TAG+="systemd", IMPORT{builtin}="path_id", ENV{SYSTEMD_WANTS}+="systemd-backlight@backlight:$name.service"
SUBSYSTEM=="leds", KERNEL=="*kbd_backlight", TAG+="systemd", IMPORT{builtin}="path_id", ENV{SYSTEMD_WANTS}+="systemd-backlight@leds:$name.service"
backlight: add minimal tool to save/restore screen brightness across reboots 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-14 07:57:02 +08:00
rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services
2013-10-14 10:31:49 +08:00
# Pull in rfkill save/restore for all rfkill devices
rules: split the rfkill subsystem rule (#6556) This patch makes sure both rules are applied to rfkill devices. Otherwise the ENV rule may be skipped if path_id fails. Fixes: #6528
2017-08-08 14:41:15 +08:00
SUBSYSTEM=="rfkill", ENV{SYSTEMD_RFKILL}="1"
SUBSYSTEM=="rfkill", IMPORT{builtin}="path_id"
rfkill: rework and make it listen on /dev/rfkill With this rework we introduce systemd-rfkill.service as singleton that is activated via systemd-rfkill.socket that listens on /dev/rfkill. That way, we get notified each time a new rfkill device shows up or changes state, in which case we restore and save its current setting to disk. This is nicer than the previous logic, as this means we save/restore state even of rfkill devices that are around only intermittently, and save/restore the state even if the system is shutdown abruptly instead of cleanly. This implements what I suggested in #1019 and obsoletes it.
2015-10-01 20:32:48 +08:00
SUBSYSTEM=="misc", KERNEL=="rfkill", TAG+="systemd", ENV{SYSTEMD_WANTS}+="systemd-rfkill.socket"
rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services
2013-10-14 10:31:49 +08:00
rules: systemd - remove legacy "ram" from block device blacklist
2015-03-12 23:28:38 +08:00
# Asynchronously mount file systems implemented by these modules as soon as they are loaded.
rules: don't limit some of the rules to the "add" action 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-16 08:51:24 +08:00
SUBSYSTEM=="module", KERNEL=="fuse", TAG+="systemd", ENV{SYSTEMD_WANTS}+="sys-fs-fuse-connections.mount"
SUBSYSTEM=="module", KERNEL=="configfs", TAG+="systemd", ENV{SYSTEMD_WANTS}+="sys-kernel-config.mount"
udev: asynchronously mount fuse/confifgs as soon as the kmods are loaded
2011-09-22 09:02:15 +08:00
udev: install rules file that ignore those nasty useless tty devices by default
2010-04-11 01:18:21 +08:00
LABEL="systemd_end"
Reference in New Issue Copy Permalink