On Sat, 25.12.10 17:25, Ozan Çağlayan ([email protected]) wrote: > > On 25.12.2010 17:14, Lennart Poettering wrote: > >On Fri, 26.11.10 16:43, Ozan Çağlayan ([email protected]) wrote: > > > >> Can't plymouthd be started as the very first service as possible (or is it > >>already)? Because the progress on my theme doesn't even progress at all ;) > > > >plymouth currently requires the video kmods to be loaded. I discussed > >this briefly with Ray and asked him to maybe change plymouth to actively > >listen to udev events so that we can start it early and that it makes > >use of the video device as soon as they show up instead of delaying this > >to the point where we enumerated and settled everything. (something > >similar is true for the input devices). > > A lot of distributions puts those modules in their initramfs and spawns > plymouthd in initramfs. So I think the > plymouthd startup units in systemd will not be much used by > distributions (for booting, not shutdown). Am I wrong?
Loading an initrd via BIOS calls from within grub is actually very slow. It is my intention to support both initrd and initrd-less boots by default, so that a smart boot loader could support both and switch automatically depending whether the root disk can be found trivially (also embedded people don't use initrds anyway). Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
