Re: The case of udev and the missing /dev/input/mice

[Scott James Remnant <scott@ubuntu.com>]

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

On Wed, 2005-09-21 at 11:51 +0200, Kay Sievers wrote:

> On Wed, Sep 21, 2005 at 03:38:06AM +0100, Scott James Remnant wrote:
> > Background: in the upcoming Ubuntu 5.10 we've been having some problems
> > with /dev/input/mice not being created on startup despite the "mousedev"
> > module being hard-loaded early in the boot sequence.
> > (http://bugzilla.ubuntu.com/show_bug.cgi?id=12915 for those interested).
> > 
> > Debian has had similar problems too (http://bugs.debian.org/317333) and
> > found that starting udevd earlier manually seemed to fix it.
> 
> Yes, that's a good way to fix it.
> 
One thing I'd like to see changed in udevd is to move the
init_udevd_socket() and init_uevent_netlink_sock() calls to above the
daemonization; that way when you call "udevd --daemon" from the init
script, you *know* that the next command may cause a netlink event.

Right now there's an unknown amount of time between calling "udevd
--daemon" and being able to safely "modprobe".

This'd also mean that udevd could exit with an error status if it's
unable to create the necessary sockets; rather than the child exiting
and the status being lost.

Scott
-- 
Scott James Remnant
scott@ubuntu.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]