The problem on my system is clearly with mountall. I went to the source repository and grabbed a couple of binaries, 0.2.0 and 0.1.8, which I then subbed into my system. Mountall 0.2.0 failed at the same place, mountall 0.1.8 works great. I'm running 2.6.31.3 without an initrd. This is a switch of the binary only; no config files were changed or other steps taken.
This raises another issue. The online rumor is Ubuntu generally will no longer support linux booting without an initrd. If this is the case I'll politely go away and be done with Ubuntu, but it would be good to know if my "bug" is something that simply won't be addressed. Here's what appears on my console at the point of failure: mountall:/proc/filesystems: no such file or directory init: mountall main process (1284) killed by SEGV signal rm.: cannot remove `/forcefsck': Read-only file system init: mountall post-stop process (1285) terminated with status 1 It then goes on to find the keyboard and a usb card reader (four-slot, so all this takes about 20 lines) and, when I would expect it to mount the root filesystem, nothing happens. It just hangs. -- karmic - mountall fails to mount filesystem on boot https://bugs.launchpad.net/bugs/447747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
