From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] Give a hint when 'udevd' is ready to operate
Date: Sat, 29 Apr 2006 09:08:54 +0000 [thread overview]
Message-ID: <877j587nq1.fsf@kosh.bigo.ensc.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
Hello,
please apply the attached patch. It creates the '/dev/.udev' directory
when 'udevd' is ready to operate.
This helps init methods like 'initng' or 'minit' to stop future
processing (e.g. invoking 'udevtrigger') until 'udevd' is fully
initialized. Currently, there does not seem to exist a way to wait
for 'udevd' (resp. to check whether it is ready) and issued uevent's
may disappear silently.
With this patch, the init methods can test for /dev/.udev (e.g. waiting
actively or using inotify) after 'udevd' has been started.
Enrico
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: creates /dev/.udev upon startup --]
[-- Type: text/x-patch, Size: 283 bytes --]
--- udev-091/udevd.c.startup 2006-04-25 22:39:59.000000000 +0200
+++ udev-091/udevd.c 2006-04-28 10:00:48.000000000 +0200
@@ -946,6 +946,8 @@
chdir("/");
umask(022);
+ create_path(UDEV_ROOT);
+
/* become session leader */
sid = setsid();
dbg("our session is %d", sid);
next reply other threads:[~2006-04-29 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 9:08 Enrico Scholz [this message]
2006-04-29 12:46 ` [PATCH] Give a hint when 'udevd' is ready to operate Scott James Remnant
2006-04-29 12:58 ` Kay Sievers
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=877j587nq1.fsf@kosh.bigo.ensc.de \
--to=enrico.scholz@informatik.tu-chemnitz.de \
--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).