OXIESEC PANEL
- Current Dir:
/
/
lib
/
udev
/
rules.d
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
10/28/2024 06:50:46 AM
rwxr-xr-x
📄
01-md-raid-creating.rules
321 bytes
01/14/2020 07:10:59 PM
rw-r--r--
📄
40-vm-hotadd.rules
655 bytes
03/02/2023 12:58:02 PM
rw-r--r--
📄
50-apport.rules
165 bytes
11/11/2019 09:57:56 PM
rw-r--r--
📄
50-firmware.rules
210 bytes
07/01/2021 03:44:19 PM
rw-r--r--
📄
50-udev-default.rules
3.53 KB
03/02/2023 12:58:02 PM
rw-r--r--
📄
55-dm.rules
7.1 KB
01/23/2020 03:45:10 PM
rw-r--r--
📄
56-lvm.rules
2.39 KB
01/23/2020 03:45:10 PM
rw-r--r--
📄
60-block.rules
620 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-cdrom_id.rules
1.05 KB
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-drm.rules
413 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-evdev.rules
974 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-input-id.rules
282 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-libgphoto2-6.rules
6.47 KB
12/23/2017 12:19:04 PM
rw-r--r--
📄
60-open-vm-tools.rules
250 bytes
09/08/2022 04:08:40 AM
rw-r--r--
📄
60-persistent-alsa.rules
616 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-persistent-input.rules
2.65 KB
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-persistent-storage-dm.rules
1.75 KB
01/23/2020 03:45:10 PM
rw-r--r--
📄
60-persistent-storage-tape.rules
1.47 KB
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-persistent-storage.rules
6.37 KB
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-persistent-v4l.rules
769 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-sensor.rules
727 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
60-serial.rules
1.16 KB
01/28/2018 03:58:17 PM
rw-r--r--
📄
61-persistent-storage-android.rules
456 bytes
03/02/2023 12:58:02 PM
rw-r--r--
📄
63-md-raid-arrays.rules
2.08 KB
01/14/2020 07:10:59 PM
rw-r--r--
📄
64-btrfs-dm.rules
387 bytes
03/12/2018 11:04:27 PM
rw-r--r--
📄
64-btrfs.rules
570 bytes
03/02/2023 12:58:02 PM
rw-r--r--
📄
64-md-raid-assembly.rules
1.41 KB
01/14/2020 07:10:59 PM
rw-r--r--
📄
66-azure-ephemeral.rules
1.91 KB
04/20/2023 09:31:09 PM
rw-r--r--
📄
66-snapd-autoimport.rules
190 bytes
12/01/2022 08:52:23 AM
rw-r--r--
📄
69-bcache.rules
1.02 KB
08/05/2020 08:44:05 PM
rw-r--r--
📄
69-lvm-metad.rules
6.51 KB
01/23/2020 03:45:10 PM
rw-r--r--
📄
69-md-clustered-confirm-device.rules
846 bytes
01/14/2020 07:10:59 PM
rw-r--r--
📄
70-iscsi-disk.rules
253 bytes
04/06/2022 07:19:56 PM
rw-r--r--
📄
70-iscsi-network-interface.rules
226 bytes
04/06/2022 07:19:56 PM
rw-r--r--
📄
70-joystick.rules
432 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
70-mouse.rules
734 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
70-power-switch.rules
568 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
70-touchpad.rules
473 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
70-uaccess.rules
2.62 KB
03/02/2023 12:58:02 PM
rw-r--r--
📄
71-power-switch-proliant.rules
461 bytes
03/02/2023 12:58:02 PM
rw-r--r--
📄
71-seat.rules
2.69 KB
03/02/2023 12:58:02 PM
rw-r--r--
📄
73-seat-late.rules
636 bytes
03/02/2023 12:58:02 PM
rw-r--r--
📄
73-special-net-names.rules
961 bytes
12/10/2021 09:15:07 AM
rw-r--r--
📄
73-usb-net-by-mac.rules
1.26 KB
12/10/2021 09:15:07 AM
rw-r--r--
📄
75-net-description.rules
452 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
75-probe_mtd.rules
174 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
78-graphics-card.rules
965 bytes
03/02/2023 12:58:02 PM
rw-r--r--
📄
78-sound-card.rules
4.7 KB
01/28/2018 03:58:17 PM
rw-r--r--
📄
80-debian-compat.rules
1.34 KB
12/09/2021 01:25:03 PM
rw-r--r--
📄
80-drivers.rules
615 bytes
01/28/2018 03:58:17 PM
rw-r--r--
📄
80-net-setup-link.rules
295 bytes
03/02/2023 12:58:02 PM
rw-r--r--
📄
85-hdparm.rules
82 bytes
02/22/2018 01:51:46 PM
rw-r--r--
📄
90-console-setup.rules
265 bytes
04/23/2019 12:04:14 PM
rw-r--r--
📄
95-dm-notify.rules
479 bytes
01/23/2020 03:45:10 PM
rw-r--r--
📄
99-systemd.rules
4.26 KB
03/02/2023 12:58:02 PM
rw-r--r--
📄
99-vmware-scsi-udev.rules
433 bytes
09/19/2022 10:14:07 PM
rw-r--r--
Editing: 69-lvm-metad.rules
Close
# Copyright (C) 2012 Red Hat, Inc. All rights reserved. # # This file is part of LVM2. # Udev rules for LVM. # # Scan all block devices having a PV label for LVM metadata. # Store this information in LVMetaD (the LVM metadata daemon) and maintain LVM # metadata state for improved performance by avoiding further scans while # running subsequent LVM commands or while using lvm2app library. # Also, notify LVMetaD about any relevant block device removal. # # This rule is essential for having the information in LVMetaD up-to-date. # It also requires blkid to be called on block devices before so only devices # used as LVM PVs are processed (ID_FS_TYPE="LVM2_member" or "LVM1_member"). SUBSYSTEM!="block", GOTO="lvm_end" ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="lvm_end" # XXX: Properly call blkid on md devices. Workaround for #793631 KERNEL!="md[0-9]*", GOTO="next" IMPORT{builtin}="blkid" LABEL="next" # If the PV label got lost, inform lvmetad immediately. # Detect the lost PV label by comparing previous ID_FS_TYPE value with current one. ENV{.ID_FS_TYPE_NEW}="$env{ID_FS_TYPE}" IMPORT{db}="ID_FS_TYPE" ENV{ID_FS_TYPE}=="LVM2_member|LVM1_member", ENV{.ID_FS_TYPE_NEW}!="LVM2_member|LVM1_member", ENV{LVM_PV_GONE}="1" ENV{ID_FS_TYPE}="$env{.ID_FS_TYPE_NEW}" ENV{LVM_PV_GONE}=="1", GOTO="lvm_scan" # Only process devices already marked as a PV - this requires blkid to be called before. ENV{ID_FS_TYPE}!="LVM2_member|LVM1_member", GOTO="lvm_end" ENV{DM_MULTIPATH_DEVICE_PATH}=="1", GOTO="lvm_end" # Inform lvmetad about any PV that is gone. ACTION=="remove", GOTO="lvm_scan" # Create /dev/disk/by-id/lvm-pv-uuid-<PV_UUID> symlink for each PV ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-id/lvm-pv-uuid-$env{ID_FS_UUID_ENC}" # If the PV is a special device listed below, scan only if the device is # properly activated. These devices are not usable after an ADD event, # but they require an extra setup and they are ready after a CHANGE event. # Also support coldplugging with ADD event but only if the device is already # properly activated. # This logic should be eventually moved to rules where those particular # devices are processed primarily (MD and loop). # DM device: KERNEL!="dm-[0-9]*", GOTO="next" ENV{DM_UDEV_PRIMARY_SOURCE_FLAG}=="1", ENV{DM_ACTIVATION}=="1", GOTO="lvm_scan" GOTO="lvm_end" # MD device: LABEL="next" KERNEL!="md[0-9]*", GOTO="next" IMPORT{db}="LVM_MD_PV_ACTIVATED" ACTION=="add", ENV{LVM_MD_PV_ACTIVATED}=="1", GOTO="lvm_scan" ACTION=="change", ENV{LVM_MD_PV_ACTIVATED}!="1", ENV{LVM_MD_PV_ACTIVATED}="1", GOTO="lvm_scan" ACTION=="add", KERNEL=="md[0-9]*p[0-9]*", GOTO="lvm_scan" ENV{LVM_MD_PV_ACTIVATED}!="1", ENV{SYSTEMD_READY}="0" GOTO="lvm_end" # Loop device: LABEL="next" KERNEL!="loop[0-9]*", GOTO="next" ACTION=="add", ENV{LVM_LOOP_PV_ACTIVATED}=="1", GOTO="lvm_scan" ACTION=="change", ENV{LVM_LOOP_PV_ACTIVATED}!="1", ENV{LVM_LOOP_PV_ACTIVATED}="1", GOTO="lvm_scan" ENV{LVM_LOOP_PV_ACTIVATED}!="1", ENV{SYSTEMD_READY}="0" GOTO="lvm_end" # If the PV is not a special device listed above, scan only if necessary. # For "direct_pvscan" mode (see below), this means run rules only an ADD events. # For "systemd_background" mode, systemd takes care of this by activating # the lvm2-pvscan@.service only once. LABEL="next" TEST!="/run/systemd/system", ACTION!="add", GOTO="lvm_end" TEST=="/run/systemd/system", ACTION!="add|change", GOTO="lvm_end" LABEL="lvm_scan" ENV{SYSTEMD_READY}="1" # The method for invoking pvscan is selected at build time with the option # --(enable|disable)-udev-systemd-background-jobs to "configure". # On modern distributions with recent systemd, it's "systemd_background"; # on others, "direct_pvscan". TEST!="/run/systemd/system", GOTO="direct_pvscan" TEST=="/run/systemd/system", GOTO="systemd_background" LABEL="systemd_background" # The table below summarises the situations in which we reach the LABEL="lvm_scan" # in the "systemd_background" case. # Marked by X, X* means only if the special dev is properly set up. # The artificial ADD is supported for coldplugging. We avoid running the pvscan # on artificial CHANGE so there's no unexpected autoactivation when WATCH rule fires. # N.B. MD and loop never actually reaches lvm_scan on REMOVE as the PV label is gone # within a CHANGE event (these are caught by the "LVM_PV_GONE" rule at the beginning). # # In this case, we simply set up the dependency between the device and the pvscan # job using SYSTEMD_ALIAS (which sets up a simplified device identifier that # allows using "BindsTo" in the sytemd unit file) and SYSTEMD_WANTS (which tells # systemd to start the pvscan job once the device is ready). # We need to set these variables for both "add" and "change" events, otherwise # systemd may loose information about the device/unit dependencies. # # | real ADD | real CHANGE | artificial ADD | artificial CHANGE | REMOVE # ============================================================================= # DM | | X | X* | | X # MD | | X | X* | | # loop | | X | X* | | # other | X | X | X | | X ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/usr/bin/systemd-run /sbin/lvm pvscan --cache $major:$minor", GOTO="lvm_end" ENV{SYSTEMD_ALIAS}="/dev/block/$major:$minor" ENV{ID_MODEL}="LVM PV $env{ID_FS_UUID_ENC} on /dev/$name" ENV{SYSTEMD_WANTS}+="lvm2-pvscan@$major:$minor.service" GOTO="lvm_end" LABEL="direct_pvscan" # The table below summarises the situations in which we reach the LABEL="lvm_scan" # for the "direct_pvscan" case. # Marked by X, X* means only if the special dev is properly set up. # The artificial ADD is supported for coldplugging. We avoid running the pvscan # on artificial CHANGE so there's no unexpected autoactivation when WATCH rule fires. # # In this case, we need to make sure that pvscan is not invoked spuriously, therefore # we invoke it only for "add" events for "other" devices. # # | real ADD | real CHANGE | artificial ADD | artificial CHANGE | REMOVE # ============================================================================= # DM | | X | X* | | X # MD | | X | X* | | # loop | | X | X* | | # other | X | | X | | X RUN+="/sbin/lvm pvscan --cache --activate ay --major $major --minor $minor", ENV{LVM_SCANNED}="1" LABEL="lvm_end"