public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: prajnoha@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/man dmsetup.8.in Date: Wed, 15 Feb 2012 12:25:00 -0000 [thread overview] Message-ID: <20120215122524.22373.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: prajnoha@sourceware.org 2012-02-15 12:25:24 Modified files: man : dmsetup.8.in Log message: Add dmsetup manpage entries for mangle command and --manglename option. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/dmsetup.8.in.diff?cvsroot=lvm2&r1=1.50&r2=1.51 --- LVM2/man/dmsetup.8.in 2012/01/18 18:52:02 1.50 +++ LVM2/man/dmsetup.8.in 2012/02/15 12:25:23 1.51 @@ -64,6 +64,9 @@ .B dmsetup mknodes .RI [ device_name ] .br +.B dmsetup mangle +.RI [ device_name ] +.br .B dmsetup reload .I device_name .RB [ \-\-table @@ -186,6 +189,17 @@ inactive table instead of the live table. Requires kernel driver version 4.16.0 or above. .TP +.IR \fB\-\-manglename \ < mangling_mode > +Mangle any character not on a whitelist using mangling_mode when +processing device-mapper device names. The names are mangled on +input and unmangled on output where the mangling_mode is one of: +none (no mangling), hex (always do the mangling) and auto +(only do the mangling if not mangled yet, do nothing if already +mangled, error on mixed; this is used by default). +Character whitelist: 0-9, A-Z, a-z, #+-.:=@_. This whitelist is +also supported by udev. Any character not on a whitelist is replaced +with its hex value (two digits) prefixed by \\x. +.TP .BR \-j | \-\-major\ \fImajor Specify the major number. .TP @@ -382,6 +396,15 @@ driver, adding, changing or removing nodes as necessary. .br .HP +.B mangle +.RI [ device_name ] +.br +Ensure existing device-mapper device name is in the correct mangled +form containing only whitelisted characters (supported by udev) and do +a rename if necessary. Any character not on the whitelist will be mangled +based on the --manglename settting. +.br +.HP .B remove .RB [ \-f | \-\-force ] .RB [ \-\-retry ]
next reply other threads:[~2012-02-15 12:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-15 12:25 prajnoha [this message] -- strict thread matches above, loose matches on Subject: below -- 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-10-22 13:12 prajnoha 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=20120215122524.22373.qmail@sourceware.org \ --to=prajnoha@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).