From: Alasdair G Kergon <agk@redhat.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Nikanth Karthikesan <knikanth@suse.de>,
Peter Rajnoha <prajnoha@redhat.com>,
Milan Broz <mbroz@redhat.com>, Alasdair G Kergon <agk@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Miklos Szeredi <miklos@szeredi.hu>,
Chris Mason <chris.mason@oracle.com>,
Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
Ian Kent <raven@themaw.net>,
dm-devel@redhat.com
Subject: Re: [dm-devel] add devname module aliases to allow module on-demand auto-loading
Date: Fri, 21 May 2010 20:32:51 +0100 [thread overview]
Message-ID: <20100521193251.GP3991@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <AANLkTimuciWfkVwn7dKVeKL38WpMiCvgAxGx4ngAankW@mail.gmail.com>
On Fri, May 21, 2010 at 08:51:49PM +0200, Kay Sievers wrote:
> The kernel itself creates /dev/mapper/control today.
Must have missed that patch:)
Userspace lvm and dm code is certainly not tied to that today.
The device node that userspace lvm and dm tools use is under the
complete control of this userspace code: it chooses the name, and
creates or fixes it if it doesn't already exist with the required
properties: anything devtmpfs is relevant only if it guessed the
right name that this *completely independent* userspace code
chooses to use and already created it exactly as required.
If we were to move to a fixed name for the control device and hand
control of that name to the kernel, then obviously this userspace
code would need adjusting to respect that.
Alasdair
next prev parent reply other threads:[~2010-05-21 19:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 16:07 add devname module aliases to allow module on-demand auto-loading Kay Sievers
2010-05-21 11:11 ` Ian Kent
2010-05-21 11:24 ` Kay Sievers
2010-05-21 15:15 ` Greg KH
2010-05-21 11:34 ` Alasdair G Kergon
2010-05-21 11:51 ` Kay Sievers
2010-05-21 13:11 ` Kay Sievers
2010-05-21 13:39 ` Nikanth Karthikesan
2010-05-21 13:55 ` Kay Sievers
2010-05-21 18:23 ` Alasdair G Kergon
2010-05-21 18:51 ` Kay Sievers
2010-05-21 19:32 ` Alasdair G Kergon [this message]
2010-05-21 20:20 ` [dm-devel] " Kay Sievers
2010-05-25 5:33 ` Luca Berra
2010-05-25 9:48 ` Alasdair G Kergon
2010-05-25 9:57 ` Kay Sievers
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=20100521193251.GP3991@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=chris.mason@oracle.com \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=miklos@szeredi.hu \
--cc=prajnoha@redhat.com \
--cc=raven@themaw.net \
--cc=tigran@aivazian.fsnet.co.uk \
/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