It must be a race between the metadata comitting to the fs and the segfault because the vm I tested this on is un-bootable without init=/bin/bash now.
On Feb 17, 2011, at 3:07 PM, Scott James Remnant <720...@bugs.launchpad.net> wrote: > The reason it doesn't cause a panic on the reboot is because the file > doesn't actually get to the filesystem! If it did, you wouldn't be able > to boot again. > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/720573 > > Title: > Segmentation fault on ".conf" file in /etc/init > > Status in Upstart: > In Progress > Status in “upstart” package in Ubuntu: > Confirmed > > Bug description: > Just create empty ".conf" file in /etc/init , and kernel panic occur > "attempting to kill init" > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/upstart/+bug/720573/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/720573 Title: Segmentation fault on ".conf" file in /etc/init -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
