On Tue, Jan 29, 2013 at 2:00 PM, Alon Bar-Lev <[email protected]> wrote: > On Tue, Jan 29, 2013 at 9:49 PM, Canek Peláez Valdés <[email protected]> wrote: > >> I would not bet on that ;) too much resistance. However it is >> certainly getting better and better: the LWN article on The Biggest >> Myths about systemd had an overwhelmingly majority of comments >> positive to systemd, and just a handful of negative comments: >> >> http://lwn.net/Articles/534210/#Comments >> >> But that is in LWN; Gentoo is way behind, I believe. > > Gentoo is not behind, it provides you the option of using systemd. > > However openrc is superior in many ways, as unlike systemd it provides > script base metadata vs static systemd units, so for example a service > can depend on other services based on LOGIC. Also, it has the nature > of virtual dependencies what systemd lacks, for example there are N > services that provides timesync, in openrc you provide timesync and > depend on timesync, in systemd there is no way to do so.
I really should not enter into this discussion (again), and even less with a Gentoo dev (BTW, thanks for all the great work). However, this: "for example there are N services that provides timesync, in openrc you provide timesync and depend on timesync, in systemd there is no way to do so" it's just a lie (or missinformation). display-manager.service and syslog.service work like this; they are soft links to the desired service (gdm.service and syslog.service, for example), and other units depend on them. They work like virtuals in Gentoo. > openrc is > working in various environments including embedded, while systemd > requires so much dependencies that it is not really usable at all > environments. I don't know about "all environments", but ProFUSION [1] works in embedded systems and several of its developers are systemd upstream. Also GENIVI, the standardized common software platform for developing in-vehicle infotainment (IVI), uses systemd. > openrc can be used correctly in chroot environment, > while systemd is inoperative. I know it's not exactly the same, but with systemd we have systemd-nspawn, which I (IMHO) consider far superior: man 1 systemd-nspawn. > openrc supports extra commands for > services, while systemd enforces only start/stop sequence. I can go on > an on. Yeah, OpenRC needs zap, because sometimes a daemon ends unexpectedly, and OpenRC is unable to detect it. I would not call this an advantage, though. > Just because there is hype of some branding, does not mean it is better. I believe it's better, but it's only my opinion; it's certainly better for my use-cases. I don't want to impose systemd on anyone, but I would be really happy if I could *easily* uninstall OpenRC from Gentoo, since I don't use it. I'm using an ovelay [2] right now, but is far from optimal. And, BTW, I didn't mean "behind" in the sense that Gentoo doesn't support systemd; I meant "behind" in the sense that us systemd users get a lot flak just by mention it in the list. [1] http://www.profusion.mobi/ [2] https://github.com/canek-pelaez/gentoo-systemd-only Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
