On Fri, Nov 9, 2012 at 7:11 PM, Keith Dart <ke...@dartworks.biz> wrote: > Re > 509D8E00.4030208@coolmail.se509D8E00.4030208@coolmail.sek7k1hn$ce6$1...@ger.gmane.org, > Dale said: >> I don't worry about boot up times much either. Here is why: > > > I was thinking of converting to systemd on my Gentoo laptop. There I do > boot frequently, and could benefit from quicker bootups.
As 微蔡 said, fast boots is only one of the many advantages that systemd offers. It's probably the most user-visible, though. > So I'm happy > to some success stories with it, since I've been holding off on taking > that plunge. We have had some of those lately. I believe João Matos just did the switch some weeks ago, using KDE. I did it almost two years ago, around December 2010, using GNOME (then 2, now 3). I haven't heard any insurmountable problem when switching: if you are a regular desktop or simple server user, it probably will work without you needing to do anything special (except using init=/usr/bin/systemd in your kernel command line and maybe needing to reemerge a couple of packages with USE="systemd"). If you use something more complicated (RAID, LVM, NFS, that kind of stuff), you probably will need to enable or perhaps change a couple of services, but that's it. If you use a not very common daemon, maybe you will need to write its service file; but it's ridiculous easy (specially when compared to sysvinit scripts). Just a word of advice: if you are a normal laptop user, systemd has replaced most of the functionality of consolekit; so if you boot with systemd, several packages need to have enable the systemd USE flag (and the consolekit one disabled). In particular, pambase and polkit need to set either systemd or consolekit, but cannot set both. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
