All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Give a hint when 'udevd' is ready to operate
Date: Sat, 29 Apr 2006 14:11:34 +0000	[thread overview]
Message-ID: <87psj05v55.fsf@kosh.bigo.ensc.de> (raw)
In-Reply-To: <877j587nq1.fsf@kosh.bigo.ensc.de>

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

Kay Sievers <kay.sievers@vrfy.org> writes:

>> 	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,

Does not work; the first call to export_initial_seqnum() (before fork())
is a noop because

|        strlcpy(filename, udev_root, sizeof(filename));
|        strlcat(filename, "/" EVENT_SEQNUM, sizeof(filename));
|        fd = open(filename, O_WRONLY|O_TRUNC|O_CREAT, 0644);

fails due to the non-existing '/dev/.udev' path. So, my patch should be
applied earlier


|         udev_rules_init(&rules, 1);
|
| +       create_path(udev_root);
|         export_initial_seqnum();
|
|         if (daemonize) {



Enrico

[-- Attachment #2: Type: application/pgp-signature, Size: 480 bytes --]

  parent reply	other threads:[~2006-04-29 14:11 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
2006-04-29 13:12 ` Enrico Scholz
2006-04-29 14:11 ` Enrico Scholz [this message]
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=87psj05v55.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.