From: prajnoha@sourceware.org <prajnoha@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/udev 12-dm-permissions.rules
Date: 22 Sep 2009 12:03:33 -0000 [thread overview]
Message-ID: <20090922120333.1729.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: prajnoha at sourceware.org 2009-09-22 12:03:33
Modified files:
udev : 12-dm-permissions.rules
Log message:
Add some advisory comments for users in 12-dm-permissions.rules.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/udev/12-dm-permissions.rules.diff?cvsroot=lvm2&r1=1.2&r2=1.3
--- LVM2/udev/12-dm-permissions.rules 2009/09/11 16:05:20 1.2
+++ LVM2/udev/12-dm-permissions.rules 2009/09/22 12:03:32 1.3
@@ -1,7 +1,12 @@
# Udev rules for device-mapper devices.
#
-# These rules set permissions for DM devices. There are some environment
-# variables set that can be used:
+# These rules set permissions for DM devices.
+#
+# This file is considered to be a template where users can put their
+# own entries and then put a copy of it manually to a usual place with
+# user-edited udev rules (usually /etc/udev/rules.d).
+#
+# There are some environment variables set that can be used:
# DM_UDEV_RULES_VSN - DM udev rules version
# DM_NAME - actual DM device's name
# DM_UUID - UUID set for DM device (blank if not specified)
@@ -15,6 +20,7 @@
ACTION!="change", GOTO="dm_end"
ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="dm_end"
-#ENV{DM_NAME}=="my_device", OWNER:="peter", GROUP:="peter", MODE:="644"
+# Just an example...
+# ENV{DM_NAME}=="my_device", OWNER:="peter", GROUP:="peter", MODE:="644"
LABEL="dm_end"
next reply other threads:[~2009-09-22 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 12:03 prajnoha [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 15:10 LVM2/udev 12-dm-permissions.rules prajnoha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090922120333.1729.qmail@sourceware.org \
--to=prajnoha@sourceware.org \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.