On Sat, 2005-11-05 at 19:48 +0100, Pozsar Balazs wrote: > On Sat, Nov 05, 2005 at 06:31:04PM +0100, Kay Sievers wrote: > > I've got these messages several times on the experimental SUSE too, > > but can't reproduce it so far, even without Rusty's patch to modprobe > > they have disappeared. See here for the details: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333052 > > > Just to let you know, I've also met this problem (on another distro), > and did not know about this bugreport until now. > So I've done another workaround: modprobe already parses /proc/modules > to check whether the modules needed are already loaded, and this file > also shows us the state of the modules, being "Loading", "Live" or > "Unloading". > > With my patch, modprobe waits until the needed modules come out of the > "Loading" or "Unloading" state.
Yes, this was going to be my solution. However, we only need to resort to this is locking fails (read-only root filesystem). Rusty. -- A bad analogy is like a leaky screwdriver -- Richard Braakman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
