From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Give a hint when 'udevd' is ready to operate
Date: Sat, 29 Apr 2006 12:58:11 +0000 [thread overview]
Message-ID: <20060429125811.GA13319@vrfy.org> (raw)
In-Reply-To: <877j587nq1.fsf@kosh.bigo.ensc.de>
On Sat, Apr 29, 2006 at 01:46:20PM +0100, Scott James Remnant wrote:
> On Sat, 2006-04-29 at 11:08 +0200, Enrico Scholz wrote:
>
> > please apply the attached patch. It creates the '/dev/.udev' directory
> > when 'udevd' is ready to operate.
> >
> This isn't needed.
>
> Start udevd with the --daemon argument, it won't go into the background
> until it's ready to process events.
>
> So the following code works:
>
> udevd --daemon
> udevtrigger
Yeah, that is the usual way and udevd makes sure not to return before
it's fully initialized. Waiting for a file from a daemon, just because
the minit-like stuff tries to be smart (daemons don't detach) sounds
weird. Anyway, the current udevd exports the seqnum of the kernel, so
one can wait for that, even when it's a silly workaround a problem that
does not exist in reality.
Kay
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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-04-29 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 9:08 [PATCH] Give a hint when 'udevd' is ready to operate Enrico Scholz
2006-04-29 12:46 ` Scott James Remnant
2006-04-29 12:58 ` Kay Sievers [this message]
2006-04-29 13:12 ` Enrico Scholz
2006-04-29 14:11 ` Enrico Scholz
2006-04-29 14:44 ` David Gómez
2006-04-30 0:14 ` 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=20060429125811.GA13319@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).