Date: Wed, 15 Sep 2004 00:47:31 +0200
From: Andrea Arcangeli <andrea@novell.com>
To: Greg KH <greg@kroah.com>
Cc: "Marco d'Itri" <md@Linux.IT>, "Giacomo A. Catenazzi" <cate@pixelized.ch>,
       linux-kernel@vger.kernel.org
Subject: Re: udev is too slow creating devices
Message-ID: <20040914224731.GF3365@dualathlon.random>
References: <41473972.8010104@debian.org> <41474926.8050808@nortelnetworks.com> <20040914195221.GA21691@kroah.com> <414757FD.5050209@pixelized.ch> <20040914213506.GA22637@kroah.com> <20040914214552.GA13879@wonderland.linux.it> <20040914215122.GA22782@kroah.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040914215122.GA22782@kroah.com>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 847
Lines: 15

On Tue, Sep 14, 2004 at 02:51:22PM -0700, Greg KH wrote:
> True, so sit and spin and sleep until you see the device node.  That's
> how a number of distros have fixed the fsck startup issue.

that's more a band-aid than a fix (I can imagine a userspace hang if the
device isn't created for whatever reason), if there's no way to do
better than this if you've to run fsck (or if it's not the best to run
the fsck inside the dev.d scripts), then probably this needs better
fixing. is such a big problem to execute a sys_wait4 to wait the udev
userspace to return before returning from the insmod syscall?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/