On Thu, Aug 6, 2015 at 1:17 PM, James` <wirel...@tampabay.rr.com> wrote: > Jc García <jyo.garcia <at> gmail.com> writes: > >> > I'm not saying push one over the other, but explain and delineate >> > that choice >> > *early* in the handbook. WE owe the larger linux community that wisdom:: >> > that gentoo has made peace with systemd and openrc:: imho. > >> OpenRC is there on the stage3, systemd isn't, if you don't think about >> systemd you get an OpenRC installation, I think it would confuse more >> people to talk about choosing init system(especially noobs) right at >> the beginning of the handbook. > > I think during the installation (before the reboot) lots of software > can be installed or removed. So that means that systemd and companion > packages are part of the installation. And systemd is a choice during the > profile selection part of an installation. >
++ I think the systemd install instructions really need to be folded into the main handbook. Otherwise you end up doing the two in parallel. I just went through the btrfs raid1 install both with openrc and systemd and found all of three lines where anything is done differently (though I didn't get into setting up network, logging, enabling services, etc). Just picking a profile is really 90% of it. Long-term there is discussion of removing sysvinit+openrc from the stage3 and just making installing it a step like installing your favorite logger or cron or MTA implementation. There is really only one blocker I'm aware of for doing this - which is fixing shell scripts which reference a deprecated functions.sh that was part of openrc previously (it has nothing to do with openrc functionally). Installing sysvinit and openrc would be really simple and fast (certainly faster than systemd), and it could of course be pulled in by a profile just as systemd is. Or maybe it stays in the stage3 but is pulled in as a default for a virtual, so that it gets depcleaned after installing systemd. There wouldn't be any blockers either way, so anybody who wants both installed could still do so. Gentoo is about choice, and we try to make most of our decisions pragmatically. Defaults are just defaults, and where it is reasonable we try not to even have defaults. In fact, if you're running a chroot or container install, you might not want any init implementation installed (though both systemd and openrc are being designed to run inside containers if desired). -- Rich
