@Clint thanks for taking over, I was pretty shocked to learn that Rolf is trying to triage this bug but does not even know what an initrd is
unfortunately this will be difficult to debug because most of the progress information I was used to see scrolling over my screen for many years is gone. It seems that Ubuntu is now depending on the initrd to do the fsck of the root-filesystem. regarding your questions: 1.) there are many howtos on how to build a kernel and configure grub to boot it. basically you need to have the ide/sata and filesystem drivers compiled into the kernel to boot without initrd. 2.) I would expect it to show the same behaviour I was used to see since ~1995: run fsck on the filesystem and show the progress 3.) see my initial post 4.) there are many reasons one would not want to use a distribution supplied kernel and probably run without an initrd. the most important reason for me is that I can boot with init=/bin/bash and fix most things upgrades have broken so far (xorg, pam,...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588624 Title: upstart fails to boot without initrd -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
