2007/5/29, David Kempe <[EMAIL PROTECTED]>: > Anders Häggström wrote: > > Anyone know why this happens? > > upstart is event driven, so things happen after other things. The login > prompt comes up, but is overwritten by other things happening in the > background. This will be different for different hardware etc, as the > event driven init works that way. > > the upside in decreased boot time, the downside is that things may > happen in strange orders sometimes... > > dave > Well.. some more downsides are that I have no control over the situation. I have no idea of which service starts in what order, or have the ability to isolate a fiew services to one runlevel and some other services to another runlevel. I think a server enviroment the boot time is not that imortant. It's much more important to be able to customize the servces and control the way they are executed.
Upstart is a great idea when it comes to desktop use, and to spawn services as they are needed when special hardware is attached and detached. But that, really, is not the case in a server enviroment, is it? I don't get the thing about "event driven", because Upstart still use the /etc/rc?.d/ directorys and runlevel S and 2 during boot. And I can still change the way services are spawned/started just by changing the order of the boot-scripts in /etc/rcS.d/ and /etc/rc2.d/ The only thing Upstart adds to this is that I don't know why it works or how it works, or for how long it will continue to work. If I can't solve this issues (it's more than just the login-messed-up-thing) with Upstart, or change back to a standard SysV-model, I will have to swich to another server platform. I don't want to, I think Ubuntu is great in many ways, but you leave me no choise. // Anders -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
