Yep, the new initscripts worked. Now just have to get my SOundBlaster Live working (correct module, worked in 8.2, not in RC3).
Alan ----- Original Message ----- From: "Alan Hughes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 7:32 PM Subject: Re: [Cooker] RC3 Bugs (second try) Thanks, I'm going to try initscripts 10 as soon as I've done a re-install. The problem with /usr is however a major headache - I never have /usr integrated with /, either at home or at work. I just hope this will be fixed for 9.0 final. For the moment I'm doing a re-install so that I can play with some of the options. The VFS message looks like the one I've seen, although I've never got a good look at it. The "Have a nice day..." bit sounds like a piece of kernel code however :-) Alan ----- Original Message ----- From: "Götz Waschk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 8:45 AM Subject: Re: [Cooker] RC3 Bugs (second try) Hi, I'd like to comment some of your problems. Am Freitag, 20. September 2002, 07:53:45 Uhr MET, schrieb [EMAIL PROTECTED]: > 2. I reformatted partitions originally created for RC2. / is mounted from > /dev/hda12 (ReiserFS), while /usr, /var, /tmp and /home are mounted from LVM > partitions (XFS). mkfs.xfs reports that it could not find the lvdisplay > command (see in ddebug.log). At the moment there are still problems with /usr on a separate partition. You could try to install again with /usr on the root partition. > 3. On booting RC3 it reported an error in /etc/init.d/usb (line 1: eval not > found). This is early on in the boot process, just after the host name is > set, but before the LVM volumes are mounted (I think). This and your USB mouse problem relate to the fact mentioned above. The usb script requires a binary from /usr, but that partition in't mounted then. This has been fixed in initscripts 10mdk. > 4. On shutting down the system I briefly saw a message in which the VFS > seemed to say that some inode where still open. The system still shut down > OK. Not sure what these messages meant, and they appeared and disappered so quickly I was not able to work out excatly what they said. I also had this problem, however I could identify the message: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... That message is from fs/super.c I am not a kernel hacker, but I think some partition didn't umount successfully, maybe you could try to disable supermount and see if this helps. -- Götz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
