From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: advice needed for gentoo bug involving lvm2/udev
Date: Tue, 06 Dec 2011 22:10:13 +0000 [thread overview]
Message-ID: <20111206221013.GA19750@linux1> (raw)
In-Reply-To: <20111003164149.GA13439@linux1>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On Tue, Oct 04, 2011 at 03:09:34AM +0200, Kay Sievers wrote:
> On Mon, Oct 3, 2011 at 18:41, William Hubbs <w.d.hubbs@gmail.com> wrote:
> > we have the following bug posted in gentoo's bugzilla:
> >
> > http://bugs.gentoo.org/show_bug.cgi?id=365227.
> >
> > The reporter is telling me that we should use --action=change instead of
> > --action=add in the cold boot sequence when dev is devtmpfs. However,
> > this doesn't seem to be the correct fix based on earlier discussions on
> > this list.
> >
> > Does anyone else have any suggestions for fixing this? My thought is
> > that the rules for lvm2 should be fixed. What does everyone else think?
>
> --action=add is still the recommended and default way of doing coldplug.
>
> It should only be done once after udevd is started though, and never
> again. All later triggers should be change only.
The reporter is now saying that --action=add does not touch nodes that
are already in the file system, so, for example, if you mount devtmpfs
on /dev then call udevadm trigger --action=add, the permissions,
ownership, etc, of nodes that already exist are not touched. So, he is
suggesting that we add another udevadm trigger call with --action=change
to the cold boot sequence.
Is this a bug in udev, or should we add this extra udevadm trigger call?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-06 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 16:41 advice needed for gentoo bug involving lvm2/udev William Hubbs
2011-10-04 1:09 ` Kay Sievers
2011-12-06 22:10 ` William Hubbs [this message]
2011-12-12 21:45 ` William Hubbs
2011-12-12 23:22 ` 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=20111206221013.GA19750@linux1 \
--to=w.d.hubbs@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).