linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev integration for device-mapper and its subsystems.
Date: Tue, 28 Apr 2009 18:45:58 +0000	[thread overview]
Message-ID: <20090428184558.GU23302@agk.fab.redhat.com> (raw)
In-Reply-To: <49F5DC36.9080309@redhat.com>

On Tue, Apr 28, 2009 at 07:41:10PM +0200, Kay Sievers wrote:
> Please do not rename kernel devices, they should match the kernel
> names. Only create SYMLINK+= to the kernel names, or change the kernel
> to ceate the proper names, which will not work I guess, so please
> leave them as they are today.
 
> In general we do not want any unneeded disconnect from kernel names
> and /dev names, and dm block devices should stay as /dev/dm-* device
> nodes.
 
The /dev/dm-* devices have been a support headache for us.  I don't know
how they first sneaked into some distros but I maintain that dm-* are
internal kernel names only of use for debugging purposes and the average
sysadmin should never have to encounter them.  If I had my way they
would never have become visible to userspace.  (Unfortunately the size
restriction on the field prevents us from replacing them with our
preferred names within the kernel, unless that's changed since
I last looked.)

There is nothing fundamental about dm-*, they are meaningless to the
user, absolutely not persistent across boots and tools may need to
change what they mean whenever there is some reconfiguration.  Their
presence causes no end of problems as they 'leak' out into initrds,
fstabs, error messages etc.  On a normal, functioning system, absolutely
nothing in userspace should ever reference them.

The namespace for dm devices is currently *only* under /dev/mapper.

If people *really* think dm devices need to appear directly in a flat
namespace in /dev (why?) then we should drop the /dev/mapper directory
and move them to /dev/mapper-vg1-lvol1 for example.  (The whole strength
of udev is that it makes it easy to do something like that, in fact.)

Alternatively, we could see about making dm uuids mandatory and
go for something like /dev/dm-<uuid>.

Alasdair
-- 
agk@redhat.com

  parent reply	other threads:[~2009-04-28 18:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 16:24 Udev integration for device-mapper and its subsystems Peter Rajnoha
2009-04-28 17:41 ` Kay Sievers
2009-04-28 18:45 ` Alasdair G Kergon [this message]
2009-04-28 19:24 ` Kay Sievers
2009-04-28 21:16 ` Milan Broz
2009-04-28 21:25 ` Kay Sievers
2009-04-29  0:28 ` Alasdair G Kergon
2009-04-29  1:16 ` Kay Sievers
2009-04-29  2:45 ` Alasdair G Kergon
2009-04-29 10:05 ` Kay Sievers
2009-04-29 11:52 ` Milan Broz
2009-04-29 12:41 ` Karel Zak
2009-04-29 12:55 ` Kay Sievers
2009-04-29 12:59 ` Hannes Reinecke
2009-04-29 13:45 ` Kay Sievers
2009-04-29 20:11 ` Peter Rajnoha
2009-04-29 20:46 ` Kay Sievers
2009-04-29 21:44 ` Peter Rajnoha

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=20090428184558.GU23302@agk.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=linux-hotplug@vger.kernel.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 NNTP newsgroup(s).