On Fri, Oct 22, 2010 at 01:21:01PM -0000, Dave Martin wrote: > Re the upstart problems, it seems bizarre to start getty in tty1 and > then kill it and run something else. I expect that upstart jobs of like > the below weren't really part of the original thinking...
> start on started x > exec stop x They certainly are part of the original thinking; in fact it's a common use case for an upstart job to stop *itself* in a pre-start script. We've just run into a bug in a corner case, perhaps because no other packages are stopping other jobs in pre-start scripts up to now. > Wouldn't it make more sense to have a linaro modification to the upstart > package, which removes of modified the tty1 job? That means having to maintain a forked version of the upstart package; it looks like this script works reliably if called 'start on started tty1' instead of 'start on starting tty1' which is what's there now, so I think that's what we should go with pending an upstart fix. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- Headless on beagle, beagle XM, does not boot into tty https://bugs.launchpad.net/bugs/652221 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
