File Manager

Hackfut Security File Manager

Current Path: /lib/udev/rules.d

📁 ..
📄 01-log-block.rules(207 B)
📄 10-console.rules(421 B)
📄 10-dm.rules(6.8 KB)
📄 11-dm-lvm.rules(2.41 KB)
📄 13-dm-disk.rules(1.5 KB)
📄 40-isdn.rules(180 B)
📄 40-multipath.rules(1012 B)
📄 40-redhat.rules(1.54 KB)
📄 42-qemu-usb.rules(405 B)
📄 50-firmware.rules(172 B)
📄 50-udev-default.rules(4.31 KB)
📄 60-alias-kmsg.rules(357 B)
📄 60-cdrom_id.rules(316 B)
📄 60-net.rules(283 B)
📄 60-persistent-alsa.rules(676 B)
📄 60-persistent-input.rules(2.18 KB)
📄 60-persistent-serial.rules(893 B)
📄 60-persistent-storage-tape.rules(1.42 KB)
📄 60-persistent-storage.rules(7.31 KB)
📄 60-persistent-v4l.rules(789 B)
📄 61-mobile-action.rules(722 B)
📄 61-option-modem-modeswitch.rules(3.95 KB)
📄 61-persistent-storage-edd.rules(532 B)
📄 61-sas-storage.rules(487 B)
📄 64-device-mapper.rules(107 B)
📄 64-md-raid.rules(1.86 KB)
📄 65-md-incremental.rules(2.69 KB)
📄 69-dm-lvm-metad.rules(4.18 KB)
📄 70-acl.rules(1.74 KB)
📄 70-hid2hci.rules(1.34 KB)
📄 71-biosdevname.rules(1.06 KB)
📄 73-idrac.rules(259 B)
📄 75-cd-aliases-generator.rules(462 B)
📄 75-net-description.rules(680 B)
📄 75-persistent-net-generator.rules(4.04 KB)
📄 75-tty-description.rules(658 B)
📄 78-sound-card.rules(4.79 KB)
📄 79-fstab_import.rules(137 B)
📄 80-drivers.rules(846 B)
📄 80-iosched.rules(584 B)
📄 80-mpath-iosched.rules(398 B)
📄 80-tuned-iosched.rules(516 B)
📄 80-tuned-mpath-iosched.rules(401 B)
📄 81-kvm-rhel.rules(92 B)
📄 81-tuned-add-disk.rules(146 B)
📄 85-regulatory.rules(295 B)
📄 88-clock.rules(291 B)
📄 89-microcode.rules(173 B)
📄 91-drm-modeset.rules(56 B)
📄 95-dm-notify.rules(492 B)
📄 95-keyboard-force-release.rules(2.85 KB)
📄 95-keymap.rules(9.76 KB)
📄 95-udev-late.rules(155 B)

Editing: 65-md-incremental.rules

# 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", \
	RUN+="/sbin/mdadm -I $env{DEVNAME}"

# 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"

Hackfut Security File Manager

Editing: 65-md-incremental.rules

Upload File

Create Folder