On Mon, 2009-10-12 at 17:40 +0000, Dave North wrote: > 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. > No, we absolutely support that - in fact it's much faster to not have an initrd if you have your storage controller and filesystem drivers built into the kernel. You lose the ability to resume from hibernate, have root on LVM or MD, etc. but I don't think those are particularly compelling anyway ;)
> 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 > This is bug 447947, I uploaded a fix for that last night. Scott -- Scott James Remnant sc...@ubuntu.com -- 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
