On Wed, 2006-09-06 at 21:51, maximilian attems wrote: > > From: Tim Phipps <[EMAIL PROTECTED]> > > To: Debian Bug Tracking System <[EMAIL PROTECTED]> > > I've traced a couple of error messages down to upslash_write being used > > after initramfs.bottom has run. usplash_write tries to use stuff in /dev > > but initramfs.bottom has moved /dev to $rootmnt/dev. The following patch > > replaces the empty /dev with a symlink to the new location. It has to be > > a symlink rather than a 'mount -o bind' so that nuke can remove it later > > just before pivot_root. > > the analysis looks right, > didn't see any errors when usplash is running due to splash bootarg. > errors seems harmless, haven't had time to check the fix, > that looks right at the first sight. > It's quite hard to see the error messages, this all happens before bootlogd runs and usplash is usually running so you can't see messages on the console. I only noticed it because I was timeouts due to NFS mounting taking too long. It's a very minor problem for usplash but I thought I should report it because if other things run after udev moves /dev it could be difficult to debug.
Cheers, Tim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
