From: prajnoha@sourceware.org <prajnoha@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/man dmsetup.8.in
Date: 22 Oct 2009 13:12:20 -0000 [thread overview]
Message-ID: <20091022131220.3689.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: prajnoha at sourceware.org 2009-10-22 13:12:20
Modified files:
man : dmsetup.8.in
Log message:
Add manpage entry for dmsetup udevflags.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/dmsetup.8.in.diff?cvsroot=lvm2&r1=1.26&r2=1.27
--- LVM2/man/dmsetup.8.in 2009/09/23 12:52:52 1.26
+++ LVM2/man/dmsetup.8.in 2009/10/22 13:12:20 1.27
@@ -64,6 +64,9 @@
.B dmsetup mknodes
.I [device_name]
.br
+.B dmsetup udevflags
+.I cookie
+.br
.B dmsetup udevcomplete
.I cookie
.br
@@ -303,6 +306,18 @@
.IP \fBtargets
.br
Displays the names and versions of the currently-loaded targets.
+.br
+.IP \fBudevflags
+.I cookie
+.br
+Parses given cookie value and extracts any udev control flags encoded.
+The output is in environment key format that is suitable for use in udev
+rules. If the flag has its symbolic name assigned then the ouput is
+DM_UDEV_FLAG_<flag_name>='1', DM_UDEV_FLAG<flag_position>='1' otherwise.
+Subsystem udev flags don't have symbolic names assigned and these ones are
+always reported as DM_SUBSYSTEM_UDEV_FLAG<flag_position>='1'. There are
+16 udev flags altogether.
+.br
.IP \fBudevcomplete
.I cookie
.br
next reply other threads:[~2009-10-22 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 13:12 prajnoha [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-15 12:25 LVM2/man dmsetup.8.in prajnoha
2011-11-30 22:32 agk
2011-11-13 1:41 agk
2011-03-10 13:11 mbroz
2010-02-15 16:32 prajnoha
2009-11-06 1:41 agk
2009-04-23 12:20 agk
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=20091022131220.3689.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.