[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")
Justin L Werner
936667 at bugs.launchpad.net
Mon Mar 19 13:17:28 UTC 2012
The --no-log will be a kernel command line option.
If you're on x86 or amd64, you would stop the Grub boot, and manually
edit the kernel cmdline to add the --no-log. Then, once you're up and
running, you would edit /etc/default/grub changing GRUB_CMDLINE_LINUX,
to affect both normal and recovery modes. Once you've done that, you
run 'update-grub' and you should be good to go.
Ref: https://help.ubuntu.com/community/Grub2
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/936667
Title:
Upstart early job logging causes boot failure for systems with no
initramfs (error is "No available ptys")
Status in “upstart” package in Ubuntu:
Confirmed
Bug description:
When booting 12.04 after a recent update, I see "init(4): no available
ptys" being displayed faster than a machine gun. When I add --no-log
as a kernel option and I'm able to boot just fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667/+subscriptions
More information about the foundations-bugs
mailing list