Please update the documentation to include an alternative install using systemd as the default init system.
Just a heads-up that this is indeed on the short-list of things to do soon.
Any progress on this bug, @Swift? I see a small note concerning Systemd in the AMD64 handbook: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Optional:_Using_systemd I'll have to walk through the Systemd article to see if instructions are clear enough...
Upon further review, I would agree: installation instructions for using Systemd as an alternate init system are not inherently clear from the systemd article itself. There is quite a bit unnecessary text in the main Systemd article (such as the Services and Troubleshooting sections) that are not necessary for a user to get Systemd installed and services configured. I suggest creating a sub-article on the Systemd article that can clearly pick up exactly where the current Handbook(s) leaves off which has instructions that are to the point. Either that or move the Services and Troubleshooting section to Systemd/Guide and have the main Systemd article be the place users will go to for the additional Handbook instructions necessary to get Systemd installed...
(In reply to Matthew Marchese from comment #3) > > I suggest creating a sub-article on the Systemd article that can clearly > pick up exactly where the current Handbook(s) leaves off which has > instructions that are to the point. Either that or move the Services and > Troubleshooting section to Systemd/Guide and have the main Systemd article > be the place users will go to for the additional Handbook instructions > necessary to get Systemd installed... Picking up where the main handbook leaves off isn't really the right approach. That results in extra steps getting openrc configured that aren't necessary if you're using systemd. In fact, if you're using a systemd stage3 then you really need to change a lot of stuff in the current handbook, not just a few steps. Using eselect to set LINGUAS for example is the wrong way to go about it if you're using a systemd stage3. If you're using a default stage3 and installing systemd then you'll want to use eselect, but do that BEFORE you emerge @world and install systemd.
I'm finally getting back around to this... Rich, I didn't explain my reasoning clearly. There's a point in the Handbook where a fork can occur: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Optional:_Using_systemd I'm essentially saying from that point onward the reader would move away from the Handbook in order to follow the systemd installation/configuration path. From a brief review of the Handbook, however, there are a few more sections the reader would need to cover (in addition to the Installation and Configuration sections of the systemd article itself) in order to have an operational installation: 1. Configuring the kernel 2. Configuring the system 3. Finalizing I'm still not exactly sure the best method to fixing this... If I create any "Handbook extension" articles outside of Handbook: namespace they are able to be broken by public wiki edits, however being a wiki admin I could restrict editing of these pages specifically. Any suggestions on how to best proceed?
(In reply to Matthew Marchese from comment #5) > I'm finally getting back around to this... > > Rich, I didn't explain my reasoning clearly. There's a point in the Handbook > where a fork can occur: > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Optional: > _Using_systemd > > I'm essentially saying from that point onward the reader would move away > from the Handbook in order to follow the systemd installation/configuration > path. Again, I don't think any fork is necessary. Also, you need to start sooner than that section, at picking a profile. > > From a brief review of the Handbook, however, there are a few more sections > the reader would need to cover (in addition to the Installation and > Configuration sections of the systemd article itself) in order to have an > operational installation: > > 1. Configuring the kernel > 2. Configuring the system > 3. Finalizing > > I'm still not exactly sure the best method to fixing this... I would just incorporate the instructions into each step. In the kernel config if configuring manually, select support for the desired service manager. For an initramfs, include both dracut and genkernel instructions, and this has to be done after updating world (and emerging world should be done after setting locale/etc so that systemd picks it up). For networking include instructions for networkd as well, and we should probably include other network managers as well. For system logger and cron offer optional systemd equivalents. Anytime there is an instruction to use rc-update there should be a systemctl equivalent. Keep in mind that a lot of this stuff has multiple options under either openrc or systemd. That is why it doesn't make sense to fork things, because then you need to support 3 different network managers with 2 different service managers, when really only one or two lines differs between them. There aren't actually that many differences between configuring Gentoo under systemd or openrc, since configuring the service manager itself doesn't involve much work. Most of the handbook concerns other software which can work under either.
Many years later we can finally close this bug. systemd steps are merged into the handbooks, and we have revised the previously mentioned section which suggested the systemd article be followed: https://wiki.gentoo.org/index.php?title=Handbook:Parts/Blocks/Systemd&diff=prev&oldid=1200459
