Regarding to your wish to stay away from systemd: I wasted much time with bad emotions when fighting against systemd, when Arch Linux made the transition. Many others had similar emotions and some of them were banned from the Arch mailing list. Don't waste your energy in the same way, systemd will come and it's not the end of the world.
Sure, some things, e.g. journalctl are a PITA, OTOH I don't need to chroot, since systemd comes with a more comfortable solution: [rocketmouse@archlinux ~]$ llmount -w debi386; sudo systemd-nspawn -D /mnt/debi386 [sudo] password for rocketmouse: Spawning namespace container on /mnt/debi386 (console is /dev/pts/1). Init process in the container running as PID 31159. root@debi386:~# ;). There are pros and cons and you will become used to systemd. A libsystem-whatever dependency even wont break you current SysVinit/intiscripts process and it doesn't need much space on your HDD. IMO you shouldn't care about it. JFTR, when Arch made the transition to systemd, I wasn't cool, I behaved like a psychopath. Retrospectively it was just wasting energy and time. I was an idiot. _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list