Quoting Mark - Syminet ([email protected]): > >> Is any of this discussable? > > Anyone?
Thanks for sending four copies of your mail :) > The worst one here is the fact that during bootup fsck's, there is no > longer any progress bar showing status. No big deal for a small > single disk system but If your server has a multi-terabyte drive > array, fscks can take hours to complete Yep. Another annoyance introduced by plymouth. > This is why if you "hack" plymouth out of your system, you will notice > that you only see output from the old SysV scripts still living in > /etc/init.d - but you will see no output for jobs that have been > converted to upstart. Yes. And no. If you also use INIT_VERBOSE=yes as a kernelparam, you'll at least see what upstart is starting & stopping and where in the bootprocess you actually are... > Maybe some devs can chime in here but from what I understand, upstart > is here to stay come hell or high water, so any solution is going to > have to work best practice with upstart/plymouth, with no way to get > back old behavior. I wish upstart had some sort of mechanism to talk > through a plain oldschool console too, but it appears that this isn't > possible? Since 'old style' init scripts can still talk to the text console, why wouldn't upstart be able to do so? As i wrote in my original mail, would there be a possibility to implement tee(1) functionality in upstart for example? Make upstart verbose-but-not-debugging-verbose? It's blatantly clear i am not the only one aggravated by these changes in Ubuntu Server and i think it's a shame none of the people involved in this decisionmaking are responding to this thread. -Sndr. -- | Showering in clothes shows you're crazy. Showering nude shows your nuts. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
