From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: cold plugging
Date: Sat, 14 Jan 2006 13:08:21 +0000 [thread overview]
Message-ID: <20060114130821.GB12029@vrfy.org> (raw)
In-Reply-To: <200601131415.30207.treeve@scarlet.be>
On Sat, Jan 14, 2006 at 10:57:46AM +0500, Alexander E. Patrakov wrote:
> Greg KH wrote:
>
> >On Sat, Jan 14, 2006 at 12:29:45AM +0100, Pozsar Balazs wrote:
> >
> >
> >>But the above script does not guarantee that /dev/null will be created
> >>first. It only orders the events, but as events are processed in
> >>parallel, it may well happen that a later event gets processed earlier.
> >
> >Have you seen this happen?
> >
> Yes, /dev/null is never created first even if echoing to uevent files is
> ordered by Kay's script. There are always three or four messages on boot
> about /dev/null not being found. I solved this by creating
> /lib/udev/devices/null.
Sure, /dev/null is usually created/copied by the first init script
itself, but that's not what Greg meant, you may want to run pretty
complex software for bringing up all kinds of block devices and similar,
so it's just safer to have the random, zero, mem, ... and the tty's
around, before the block devices are running. The order is mainly a
copy of what udevstart was doing in the past.
With the async events, you can wait at any point during coldplug event
triggering for the events to finish. We need to find out, what's the
best approch to do this, that's the reason none of the current alternatives
is in the udev tree itself today. I wanted to start simple and this
stupid shell script snippet, works fine for me. We'll see with what
we'll end with and if we can agree on some default, we all can use,
which would be nice.
Thanks,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-01-14 13:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 12:17 cold plugging Treeve Jelbert
2006-01-13 12:32 ` Kay Sievers
2006-01-13 16:23 ` Alexander E. Patrakov
2006-01-13 18:47 ` Darren Salt
2006-01-13 18:52 ` Greg KH
2006-01-13 19:13 ` Scott James Remnant
2006-01-13 19:15 ` Marco d'Itri
2006-01-13 20:08 ` Darren Salt
2006-01-13 23:29 ` Pozsar Balazs
2006-01-13 23:53 ` Greg KH
2006-01-14 5:00 ` Alexander E. Patrakov
2006-01-14 5:57 ` Alexander E. Patrakov
2006-01-14 8:45 ` Pozsar Balazs
2006-01-14 12:48 ` Kay Sievers
2006-01-14 13:08 ` Kay Sievers [this message]
2006-01-14 13:10 ` Alexander E. Patrakov
2006-01-14 13:27 ` Kay Sievers
2006-01-14 16:28 ` Alexander E. Patrakov
2006-01-15 4:13 ` Dmitry Torokhov
2006-01-15 22:44 ` Aras Vaichas
2006-01-16 12:36 ` Kay Sievers
2006-01-16 12:53 ` Kay Sievers
2006-01-16 12:59 ` Olivier Blin
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=20060114130821.GB12029@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).