From: Piotr Karbowski <piotr.karbowski@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and existing /dev (devtmpfs)
Date: Fri, 02 Mar 2012 00:46:44 +0000 [thread overview]
Message-ID: <4F501874.1000503@gmail.com> (raw)
In-Reply-To: <4F15CB13.1000703@gmail.com>
On 01/23/2012 06:00 PM, Kay Sievers wrote:
> On Mon, Jan 23, 2012 at 17:41, Gabor Z. Papp<gzp@papp.hu> wrote:
>
> It was always 'add' which was suggested. It was the default action,
> but it was changed to 'change' because 'add' must not be used anywhere
> else than once after bootup.
>
> Triggering 'change' has some valid use cases, not many though, and
> most of them are workarounds for broken things.
>
> Settle is only needed to block until broken subsystems catch up with
> reality during bootup, and with reality how hotplug systems work
> today. It is not pulled-in for systems which do not run broken or
> legacy tools.
> o
>
> Yes, that changed May 2010 with udev 154.
I just upgraded to udev-181 and the issue still is there. I believe the
/dev/mapper/ nodes are created by kernel's devtmpfs but the /dev/dm-*
are created by cryptsetup and lvm running in initramfs where is no udev
running. Even if I umount devtmpfs on initramfs level and let udev mount
it again, the changes will be still there. (I do mount --move to
/newroot/dev). Maybe the 'actiond' should care about already-created
nodes as well?
-- Piotr.
next prev parent reply other threads:[~2012-03-02 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:25 udev and existing /dev (devtmpfs) Piotr Karbowski
2012-01-21 22:44 ` William Hubbs
2012-01-22 20:42 ` Kay Sievers
2012-01-23 16:41 ` Gabor Z. Papp
2012-01-23 17:00 ` Kay Sievers
2012-03-02 0:46 ` Piotr Karbowski [this message]
2012-03-02 2:38 ` 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=4F501874.1000503@gmail.com \
--to=piotr.karbowski@gmail.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).