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/udev 10-dm.rules.in 11-lvm.rules
Date: Tue, 04 Aug 2009 08:05:00 -0000	[thread overview]
Message-ID: <20090804080507.23077.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	prajnoha@sourceware.org	2009-08-04 08:05:06

Modified files:
	udev           : 10-dm.rules.in 11-lvm.rules 

Log message:
	Fix a typo in udev rule (splitname, NOT namesplit)

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/udev/10-dm.rules.in.diff?cvsroot=lvm2&r1=1.1&r2=1.2
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/udev/11-lvm.rules.diff?cvsroot=lvm2&r1=1.1&r2=1.2

--- LVM2/udev/10-dm.rules.in	2009/08/03 18:44:54	1.1
+++ LVM2/udev/10-dm.rules.in	2009/08/04 08:05:06	1.2
@@ -26,7 +26,7 @@
 # only (kernels >= 2.6.29). We have to check for its existence
 # and use dmsetup tool instead to get the DM name, uuid and 
 # suspended state if the "dm" subdirectory is not present.
-# The "suspended" item was added even later (kernels >= ???),
+# The "suspended" item was added even later (kernels >= 2.6.31),
 # so we also have to call dmsetup if the kernel version used
 # is in between these releases.
 TEST=="dm", ENV{DM_NAME}="$attr{dm/name}", ENV{DM_UUID}="$attr{dm/uuid}", ENV{DM_SUSPENDED}="$attr{dm/suspended}"
--- LVM2/udev/11-lvm.rules	2009/08/03 18:44:54	1.1
+++ LVM2/udev/11-lvm.rules	2009/08/04 08:05:06	1.2
@@ -20,7 +20,7 @@
 ACTION=="add", ENV{STARTUP}!="1", GOTO="lvm_end"
 
 # Use DM name and split it up into its VG/LV/layer constituents.
-IMPORT{program}="/sbin/dmsetup namesplit --nameprefixes --noheadings --rows $env{DM_NAME}"
+IMPORT{program}="/sbin/dmsetup splitname --nameprefixes --noheadings --rows $env{DM_NAME}"
 
 # Do not create symlinks for hidden subdevices.
 ENV{DM_LV_NAME}=="?*_mlog", GOTO="lvm_end"


                 reply	other threads:[~2009-08-04  8:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090804080507.23077.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: link
Be 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).