Gecko [ cel-fi.com.my ]

Name	Size	Permission	Date
01-md-raid-creating.rules	321 B	-rw-r--r--	2022-02-23 09:38
10-dm.rules	7.1 KB	-r--r--r--	2021-05-01 15:05
11-dm-lvm.rules	2.4 KB	-r--r--r--	2021-05-01 15:05
13-dm-disk.rules	1.75 KB	-r--r--r--	2021-05-01 15:05
40-redhat-disable-dell-ir-camera.rules	135 B	-rw-r--r--	2026-04-23 14:18
40-redhat-disable-lenovo-ir-camera.rules	496 B	-rw-r--r--	2026-04-23 14:18
40-redhat.rules	1.74 KB	-rw-r--r--	2026-04-23 14:18
40-usb_modeswitch.rules	39.53 KB	-rw-r--r--	2018-04-10 23:50
42-usb-hid-pm.rules	2.16 KB	-rw-r--r--	2026-04-23 14:18
50-udev-default.rules	3.21 KB	-rw-r--r--	2026-04-23 14:18
60-alias-kmsg.rules	357 B	-rw-r--r--	2026-04-23 14:18
60-cdrom_id.rules	910 B	-rw-r--r--	2026-04-23 14:18
60-drm.rules	153 B	-rw-r--r--	2026-04-23 14:18
60-evdev.rules	532 B	-rw-r--r--	2026-04-23 14:18
60-fprint-autosuspend.rules	18.07 KB	-rw-r--r--	2018-11-01 06:53
60-keyboard.rules	821 B	-rw-r--r--	2026-04-23 14:18
60-net.rules	129 B	-rw-r--r--	2020-05-22 10:44
60-persistent-alsa.rules	616 B	-rw-r--r--	2026-04-23 14:18
60-persistent-input.rules	2.41 KB	-rw-r--r--	2026-04-23 14:18
60-persistent-serial.rules	947 B	-rw-r--r--	2026-04-23 14:18
60-persistent-storage-tape.rules	1.53 KB	-rw-r--r--	2026-04-23 14:18
60-persistent-storage.rules	7.1 KB	-rw-r--r--	2026-04-23 14:18
60-persistent-v4l.rules	769 B	-rw-r--r--	2026-04-23 14:18
60-raw.rules	326 B	-rw-r--r--	2021-02-03 09:47
61-accelerometer.rules	166 B	-rw-r--r--	2026-04-23 14:18
63-fc-wwpn-id.rules	624 B	-rw-r--r--	2020-02-04 22:31
63-md-raid-arrays.rules	2.32 KB	-rw-r--r--	2022-02-23 09:38
64-btrfs-dm.rules	387 B	-rw-r--r--	2017-08-06 16:32
64-btrfs.rules	418 B	-rw-r--r--	2026-04-23 14:18
65-md-incremental.rules	2.92 KB	-rw-r--r--	2021-11-09 01:06
69-dm-lvm-metad.rules	6.23 KB	-r--r--r--	2021-05-01 15:05
69-md-clustered-confirm-device.rules	858 B	-rw-r--r--	2022-02-23 09:38
70-mouse.rules	734 B	-rw-r--r--	2026-04-23 14:18
70-power-switch.rules	706 B	-rw-r--r--	2026-04-23 14:18
70-touchpad.rules	345 B	-rw-r--r--	2026-04-23 14:18
70-uaccess.rules	2.53 KB	-rw-r--r--	2026-04-23 14:18
71-biosdevname.rules	1.06 KB	-rw-r--r--	2019-08-08 23:01
71-seat.rules	2.3 KB	-rw-r--r--	2026-04-23 14:18
73-idrac.rules	316 B	-rw-r--r--	2026-04-23 14:18
73-seat-late.rules	596 B	-rw-r--r--	2026-04-23 14:18
75-net-description.rules	452 B	-rw-r--r--	2026-04-23 14:18
75-probe_mtd.rules	174 B	-rw-r--r--	2026-04-23 14:18
75-tty-description.rules	426 B	-rw-r--r--	2026-04-23 14:18
76-phys-port-name.rules	473 B	-rw-r--r--	2026-04-23 14:18
78-sound-card.rules	4.3 KB	-rw-r--r--	2026-04-23 14:18
80-drivers.rules	618 B	-rw-r--r--	2026-04-23 14:18
80-net-name-slot.rules	491 B	-rw-r--r--	2026-04-23 14:18
80-net-setup-link.rules	292 B	-rw-r--r--	2026-04-23 14:18
81-kvm-rhel.rules	92 B	-rw-r--r--	2020-05-22 10:44
84-nm-drivers.rules	523 B	-rw-r--r--	2020-11-10 16:58
85-nm-unmanaged.rules	1.76 KB	-rw-r--r--	2020-11-10 16:58
85-regulatory.rules	291 B	-rw-r--r--	2018-10-30 22:32
90-alsa-tools-firmware.rules	771 B	-rw-r--r--	2016-11-05 18:34
90-iprutils.rules	70 B	-rw-r--r--	2020-02-05 12:58
90-nm-thunderbolt.rules	576 B	-rw-r--r--	2020-11-10 16:58
90-vconsole.rules	441 B	-rw-r--r--	2026-04-23 14:18
91-drm-modeset.rules	56 B	-rw-r--r--	2019-08-09 00:14
95-dm-notify.rules	483 B	-r--r--r--	2021-05-01 15:05
95-udev-late.rules	155 B	-rw-r--r--	2026-04-23 14:18
98-kexec.rules	689 B	-rw-r--r--	2021-07-07 09:16
99-systemd.rules	3.98 KB	-rw-r--r--	2026-04-23 14:18

Rename

# This file causes block devices with Linux RAID (mdadm) signatures to
# automatically cause mdadm to be run.
# See udev(8) for syntax

# Don't process any events if anaconda is running as anaconda brings up
# raid devices manually
ENV{ANACONDA}=="?*", GOTO="md_end"

# Also don't process disks that are slated to be a multipath device
ENV{DM_MULTIPATH_DEVICE_PATH}=="?*", GOTO="md_end"

# We process add events on block devices (since they are ready as soon as
# they are added to the system), but we must process change events as well
# on any dm devices (like LUKS partitions or LVM logical volumes) and on
# md devices because both of these first get added, then get brought live
# and trigger a change event.  The reason we don't process change events
# on bare hard disks is because if you stop all arrays on a disk, then
# run fdisk on the disk to change the partitions, when fdisk exits it
# triggers a change event, and we want to wait until all the fdisks on
# all member disks are done before we do anything.  Unfortunately, we have
# no way of knowing that, so we just have to let those arrays be brought
# up manually after fdisk has been run on all of the disks.

# First, process all add events (md and dm devices will not really do
# anything here, just regular disks, and this also won't get any imsm
# array members either)
SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="linux_raid_member", \
	IMPORT{program}="/sbin/mdadm -I $env{DEVNAME} --export $devnode --offroot ${DEVLINKS}"
SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="linux_raid_member", \
	ENV{MD_STARTED}=="*unsafe*", ENV{MD_FOREIGN}=="no", ENV{SYSTEMD_WANTS}+="mdadm-last-resort@$env{MD_DEVICE}.timer"

# Next, check to make sure the BIOS raid stuff wasn't turned off via cmdline
IMPORT{cmdline}="noiswmd"
IMPORT{cmdline}="nodmraid"
ENV{noiswmd}=="?*", GOTO="md_imsm_inc_end"
ENV{nodmraid}=="?*", GOTO="md_imsm_inc_end"
SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="isw_raid_member", \
	RUN+="/sbin/mdadm -I $env{DEVNAME}"
LABEL="md_imsm_inc_end"

SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}=="?*", \
	RUN+="/sbin/mdadm -If $name --path $env{ID_PATH}"
SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}!="?*", \
	RUN+="/sbin/mdadm -If $name"

# Next make sure that this isn't a dm device we should skip for some reason
ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="dm_change_end"
ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="dm_change_end"
ENV{DM_SUSPENDED}=="1", GOTO="dm_change_end"
KERNEL=="dm-*", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="linux_raid_member", \
	ACTION=="change", RUN+="/sbin/mdadm -I $env{DEVNAME}"
LABEL="dm_change_end"

# Finally catch any nested md raid arrays.  If we brought up an md raid
# array that's part of another md raid array, it won't be ready to be used
# until the change event that occurs when it becomes live
KERNEL=="md*", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="linux_raid_member", \
	ACTION=="change", RUN+="/sbin/mdadm -I $env{DEVNAME}"

LABEL="md_end"