From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - HOWTO
Date: Thu, 19 Feb 2004 17:35:36 +0000 [thread overview]
Message-ID: <20040219173535.GA9572@kroah.com> (raw)
In-Reply-To: <20040219011044.GA10603@vrfy.org>
On Thu, Feb 19, 2004 at 02:10:44AM +0100, Kay Sievers wrote:
> Hi Greg,
> very very nice to see that we are capable to do this now.
> Did you try to use udevsend in the start_udev script?
>
> Don't know if it makes sense, maybe the nosleep stuff is not
> neccessary with udevsend, but I just want to know if it works.
> I've put the "no SEQNUM" logic in there to bypass the
> reordering specially for this case :)
Hm, no, udevsend can't work in a "cold boot" type situation like this
one, as we need all of the devices available in /dev as soon as the
script is finished (if you look at Red Hat's scripts they instantly
start writing data to the different tty devs).
The nosleep stuff is there to just make the initial startup faster.
It's no fun waiting for udev to time out for devices that we know will
never get a device symlink (like floppy and tty devices.)
Does that help?
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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:[~2004-02-19 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 1:10 udev - HOWTO Kay Sievers
2004-02-19 17:35 ` Greg KH [this message]
2004-02-20 0:28 ` Kay Sievers
2004-02-20 1:48 ` Greg KH
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=20040219173535.GA9572@kroah.com \
--to=greg@kroah.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 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.