Linux sh52.ich-4.com 5.14.0-611.26.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jan 29 05:24:47 EST 2026 x86_64
LiteSpeed
Server IP : 198.143.147.58 & Your IP : 216.73.217.21
Domains :
Cant Read [ /etc/named.conf ]
User : actualbuzz
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
lib /
udev /
rules.d /
Delete
Unzip
Name
Size
Permission
Date
Action
01-md-raid-creating.rules
321
B
-rw-r--r--
2025-09-21 13:14
10-dm.rules
7.32
KB
-r--r--r--
2026-03-24 16:12
11-dm-lvm.rules
2.57
KB
-r--r--r--
2026-03-24 16:12
11-dm-mpath.rules
4.46
KB
-rw-r--r--
2026-01-28 09:19
11-dm-parts.rules
1.41
KB
-rw-r--r--
2026-01-28 09:19
13-dm-disk.rules
2.25
KB
-r--r--r--
2026-03-24 16:12
40-elevator.rules
728
B
-rw-r--r--
2026-05-05 15:44
40-redhat.rules
1.97
KB
-rw-r--r--
2026-05-05 15:44
40-usb-blacklist.rules
458
B
-rw-r--r--
2021-10-31 01:36
40-usb_modeswitch.rules
41.86
KB
-rw-r--r--
2022-02-11 12:27
50-udev-default.rules
5.28
KB
-rw-r--r--
2026-05-05 15:47
60-autosuspend.rules
704
B
-rw-r--r--
2022-10-31 18:59
60-block.rules
703
B
-rw-r--r--
2022-10-31 18:59
60-cdrom_id.rules
1.05
KB
-rw-r--r--
2022-10-31 18:59
60-drm.rules
413
B
-rw-r--r--
2022-10-31 18:59
60-evdev.rules
990
B
-rw-r--r--
2022-10-31 18:59
60-fido-id.rules
491
B
-rw-r--r--
2022-10-31 18:59
60-input-id.rules
282
B
-rw-r--r--
2022-10-31 18:59
60-net.rules
129
B
-rw-r--r--
2024-08-27 11:35
60-persistent-alsa.rules
616
B
-rw-r--r--
2022-10-31 18:59
60-persistent-input.rules
2.66
KB
-rw-r--r--
2022-10-31 18:59
60-persistent-storage-tape.rules
2.15
KB
-rw-r--r--
2022-10-31 18:59
60-persistent-storage.rules
10.65
KB
-rw-r--r--
2026-05-05 15:44
60-persistent-v4l.rules
769
B
-rw-r--r--
2022-10-31 18:59
60-sensor.rules
1.58
KB
-rw-r--r--
2022-10-31 18:59
60-serial.rules
1.11
KB
-rw-r--r--
2026-05-05 15:44
60-tpm-udev.rules
243
B
-rw-r--r--
2024-04-26 11:53
60_flashrom.rules
3.31
KB
-rw-r--r--
2022-02-11 21:46
61-scsi-sg3_id.rules
6.21
KB
-rw-r--r--
2021-11-05 23:31
62-multipath.rules
4.43
KB
-rw-r--r--
2026-01-28 09:19
63-fc-wwpn-id.rules
624
B
-rw-r--r--
2019-04-29 07:13
63-md-raid-arrays.rules
2.54
KB
-rw-r--r--
2025-09-21 13:14
63-scsi-sg3_symlink.rules
2.9
KB
-rw-r--r--
2025-03-13 12:20
64-btrfs.rules
616
B
-rw-r--r--
2026-05-05 15:47
64-md-raid-assembly.rules
2.32
KB
-rw-r--r--
2025-09-21 13:14
65-libwacom.rules
1.13
KB
-rw-r--r--
2021-12-02 00:58
65-persistent-net-nbft.rules
118
B
-rw-r--r--
2025-09-25 13:11
65-scsi-cciss_id.rules
732
B
-rw-r--r--
2017-09-18 19:15
66-azure-ephemeral.rules
1.91
KB
-rw-r--r--
2024-11-25 16:09
66-kpartx.rules
1.36
KB
-rw-r--r--
2026-01-28 09:19
66-md-auto-readd.rules
895
B
-rw-r--r--
2025-09-21 12:20
68-del-part-nodes.rules
1.12
KB
-rw-r--r--
2026-01-28 09:19
69-dm-lvm.rules
3.57
KB
-r--r--r--
2026-03-24 16:12
69-md-clustered-confirm-device.rules
858
B
-rw-r--r--
2025-09-21 13:14
70-camera.rules
281
B
-rw-r--r--
2022-10-31 18:59
70-joystick.rules
432
B
-rw-r--r--
2022-10-31 18:59
70-libfprint-2.rules
633
B
-rw-r--r--
2024-04-01 19:03
70-memory.rules
184
B
-rw-r--r--
2022-10-31 18:59
70-mouse.rules
734
B
-rw-r--r--
2022-10-31 18:59
70-nvmf-autoconnect.rules
2
KB
-rw-r--r--
2025-09-25 13:11
70-nvmf-keys.rules
267
B
-rw-r--r--
2025-09-25 13:11
70-power-switch.rules
576
B
-rw-r--r--
2022-10-31 18:59
70-touchpad.rules
473
B
-rw-r--r--
2022-10-31 18:59
70-uaccess.rules
3.66
KB
-rw-r--r--
2026-05-05 15:47
71-nvmf-netapp.rules
528
B
-rw-r--r--
2025-09-25 13:11
71-prefixdevname.rules
403
B
-rw-r--r--
2022-03-25 15:11
71-seat.rules
3.73
KB
-rw-r--r--
2026-05-05 15:47
73-seat-late.rules
643
B
-rw-r--r--
2026-05-05 15:47
75-net-description.rules
512
B
-rw-r--r--
2026-05-05 15:44
75-probe_mtd.rules
174
B
-rw-r--r--
2022-10-31 18:59
78-sound-card.rules
4.7
KB
-rw-r--r--
2022-10-31 18:59
80-drivers.rules
600
B
-rw-r--r--
2022-10-31 18:59
80-libinput-device-groups.rules
207
B
-rw-r--r--
2026-03-11 14:16
80-net-setup-link.rules
295
B
-rw-r--r--
2022-10-31 18:59
80-udisks2.rules
10.39
KB
-rw-r--r--
2025-10-20 13:58
81-net-dhcp.rules
528
B
-rw-r--r--
2022-10-31 18:59
84-nm-drivers.rules
533
B
-rw-r--r--
2025-08-01 13:31
85-nm-unmanaged.rules
1.97
KB
-rw-r--r--
2025-08-01 13:31
90-bolt.rules
359
B
-rw-r--r--
2024-02-19 08:46
90-fwupd-devices.rules
281
B
-rw-r--r--
2025-07-10 15:14
90-iprutils.rules
70
B
-rw-r--r--
2020-05-08 14:19
90-libinput-fuzz-override.rules
1.07
KB
-rw-r--r--
2026-03-11 14:16
90-nm-thunderbolt.rules
588
B
-rw-r--r--
2025-08-01 13:31
90-pipewire-alsa.rules
12.92
KB
-rw-r--r--
2024-01-10 12:30
90-vconsole.rules
489
B
-rw-r--r--
2026-05-05 15:47
91-drm-modeset.rules
56
B
-rw-r--r--
2025-03-12 18:36
95-dm-notify.rules
483
B
-r--r--r--
2026-03-24 16:12
95-upower-hid.rules
7.92
KB
-rw-r--r--
2022-02-11 07:06
95-upower-wup.rules
354
B
-rw-r--r--
2022-02-11 07:06
98-kexec.rules
695
B
-rw-r--r--
2025-09-24 06:15
99-nfs.rules
95
B
-rw-r--r--
2026-03-10 14:53
99-systemd.rules
4.92
KB
-rw-r--r--
2026-05-05 15:47
README
435
B
-rw-r--r--
2022-10-31 18:59
Save
Rename
# Set DM_MULTIPATH_DEVICE_PATH if the device should be handled by multipath SUBSYSTEM!="block", GOTO="end_mpath" KERNEL!="sd*|dasd*|nvme*", GOTO="end_mpath" ACTION=="remove", TEST=="/run/multipath/find_multipaths/$major:$minor", \ RUN+="/usr/bin/rm -f /run/multipath/find_multipaths/$major:$minor" ACTION!="add|change", GOTO="end_mpath" IMPORT{cmdline}="nompath" ENV{nompath}=="?*", GOTO="end_mpath" IMPORT{cmdline}="multipath" ENV{multipath}=="off", GOTO="end_mpath" TEST!="/etc/multipath.conf", GOTO="end_mpath" ENV{DEVTYPE}!="partition", GOTO="test_dev" IMPORT{parent}="DM_MULTIPATH_DEVICE_PATH" ENV{DM_MULTIPATH_DEVICE_PATH}=="1", ENV{ID_FS_TYPE}="none", \ ENV{SYSTEMD_READY}="0" GOTO="end_mpath" LABEL="test_dev" ENV{MPATH_SBIN_PATH}="/sbin" TEST!="$env{MPATH_SBIN_PATH}/multipath", ENV{MPATH_SBIN_PATH}="/usr/sbin" # FIND_MULTIPATHS_WAIT_UNTIL is the timeout (in seconds after the # epoch). IMPORT{db}="FIND_MULTIPATHS_WAIT_UNTIL" ENV{.SAVED_FM_WAIT_UNTIL}="$env{FIND_MULTIPATHS_WAIT_UNTIL}" # multipath -u needs to know if this device has ever been exported IMPORT{db}="DM_MULTIPATH_DEVICE_PATH" # multipath -u sets DM_MULTIPATH_DEVICE_PATH and, # if "find_multipaths smart", also FIND_MULTIPATHS_WAIT_UNTIL. IMPORT{program}=="$env{MPATH_SBIN_PATH}/multipath -u %k", \ ENV{.MPATH_CHECK_PASSED}="1" # case 1: this is definitely multipath ENV{DM_MULTIPATH_DEVICE_PATH}=="1", \ ENV{ID_FS_TYPE}="mpath_member", ENV{SYSTEMD_READY}="0", \ GOTO="stop_wait" # case 2: this is definitely not multipath, or timeout has expired ENV{DM_MULTIPATH_DEVICE_PATH}!="2", \ GOTO="stop_wait" # Code below here is only run in "smart" mode. # multipath -u has indicated this is "maybe" multipath. # Note that DM_MULTIPATH_DEVICE_PATH has the value 2 at this point. # This value will never propagate to other rules files, because # it will be reset to 1 in the "pretend_multipath" section below. # This shouldn't happen, just in case. ENV{FIND_MULTIPATHS_WAIT_UNTIL}!="?*", GOTO="end_mpath" # Be careful not to start the timer twice. ACTION!="add", GOTO="pretend_mpath" ENV{.SAVED_FM_WAIT_UNTIL}=="?*", GOTO="pretend_mpath" # At this point, we are seeing this path for the first time, and it's "maybe" multipath. # The actual start command for the timer. # # The purpose of this command is only to make sure we will receive another # uevent eventually. *Any* uevent may cause waiting to finish if it either ends # in case 1-3 above, or if it arrives after FIND_MULTIPATHS_WAIT_UNTIL. # # Note that this will try to activate multipathd if it isn't running yet. # If that fails, the unit starts and expires nonetheless. If multipathd # startup needs to wait for other services, this wait time will add up with # the --on-active timeout. # # We must trigger an "add" event because LVM2 will only act on those. RUN+="/usr/bin/systemd-run --unit=cancel-multipath-wait-$kernel --description 'cancel waiting for multipath siblings of $kernel' --no-block --timer-property DefaultDependencies=no --timer-property Conflicts=shutdown.target --timer-property Before=shutdown.target --timer-property Conflicts=initrd-cleanup.service --timer-property Before=initrd-cleanup.service --timer-property AccuracySec=500ms --property DefaultDependencies=no --property Conflicts=shutdown.target --property Before=shutdown.target --property Conflicts=initrd-cleanup.service --property Before=initrd-cleanup.service --on-active=$env{FIND_MULTIPATHS_WAIT_UNTIL} /usr/bin/udevadm trigger --action=add $sys$devpath" LABEL="pretend_mpath" ENV{DM_MULTIPATH_DEVICE_PATH}="1" ENV{SYSTEMD_READY}="0" GOTO="end_mpath" LABEL="stop_wait" # If timeout hasn't expired but we're not in "maybe" state any more, stop timer # Do this only once, and only if the timer has been started before IMPORT{db}="FIND_MULTIPATHS_WAIT_CANCELLED" ENV{FIND_MULTIPATHS_WAIT_CANCELLED}=="?*", GOTO="end_mpath" ENV{FIND_MULTIPATHS_WAIT_UNTIL}!="?*", GOTO="end_mpath" ENV{FIND_MULTIPATHS_WAIT_UNTIL}=="0", GOTO="end_mpath" ENV{FIND_MULTIPATHS_WAIT_CANCELLED}="1" RUN+="/usr/bin/systemctl stop cancel-multipath-wait-$kernel.timer" # If "multipath -u" failed, no values are imported from the program, # and we are still using the values for DM_MULTIPATH_DEVICE_PATH and # FIND_MULTIPATHS_WAIT_UNTIL that were imported from the database. # If we are in "smart" mode, we need to give up on the path now, # since this may have been the timeout event. Without the imports # from "multipath -u", we can't tell. ENV{.MPATH_CHECK_PASSED}!="?*", ENV{DM_MULTIPATH_DEVICE_PATH}="0" LABEL="end_mpath"