On Fri, 08.10.10 22:18, Andrey Borzenkov ([email protected]) wrote: > it seems that [email protected] is started in parallel with other > (legacy) initscripts. In my case it results in getty being started > very fast, and then prompt is hidden behind flood of Starting ... > messages. > > Legacy init started getty only after all initscripts are completed. is > there any defined checkpoint (target) that can be used to ensure > similar synchronization?
Not really, no. > This can probably be ignored for run level 5 as output is hidden > anyway, although even in this case switching to text console will show > some random text instead of login prompt. I believe, getty should be > delayed until all service has been started. Well, output like this kinda contradicts the idea of early logins. If you parallelize startup then output becomes intermingled. I think the right approach to this is not to show these messages by default, which is what we do on Fedora. We have discussed this forth and back with various folks a number of times, so far we couldn't come up with a nice idea to make this less ugly, except that if people really care they should implement a little ncurses based boot frontend which properly can show parallelized bootup and then gets terminated cleanly when the gettys are spawned. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
