1 |
On Mon, May 9, 2016 at 1:21 AM, Matthew Marchese <maffblaster@g.o> wrote: |
2 |
> Looks good. Nice work, fellas. |
3 |
|
4 |
++ |
5 |
|
6 |
> |
7 |
> I'll do some testing of my own on those stage tarballs so that I can write |
8 |
> some docs, unless you'd like to write them, blueness. This should ease the |
9 |
> path on the systemd "Handbook extension" idea I've been throwing around. |
10 |
> |
11 |
|
12 |
While there is no question that having systemd stage3s is a major |
13 |
improvement, it actually is likely to make the handbook more |
14 |
complicated. |
15 |
|
16 |
I've been too lazy to make the changes, but in my testing it is |
17 |
actually very simple to use the openrc handbook to install systemd. |
18 |
You just pick a systemd profile, configure the entire system using |
19 |
openrc per the handbook, and then emerge -u @world. That will install |
20 |
systemd and the Gentoo systemd ebuilds port-over the openrc |
21 |
configuration. |
22 |
|
23 |
If you start out with systemd then you need to use the systemd |
24 |
configuration tools. So, instead of using the existing procedure for |
25 |
eselect locale or setting the timezone you're going to use localectl |
26 |
and timedatectl. That means a lot more openrc and systemd-specific |
27 |
steps in the guide. Likewise, if you have a systemd-based install CD |
28 |
then you're going to want to use nspawn to mount the "chroot." I |
29 |
don't know if there is a good systemd-based rescue CD out there |
30 |
though, and ironically having systemd on the installer makes the most |
31 |
sense for both systemd and openrc installations simply because nspawn |
32 |
is so handy. Also, if you don't boot into systemd then you'll either |
33 |
need to do the configuration after rebooting, or you'll need to follow |
34 |
the steps to get dbus/etc running so that the systemd configuration |
35 |
tools work. |
36 |
|
37 |
The overall workflow will be identical. You just need to change the |
38 |
commands at many of the steps, unless they're all turned into eselect |
39 |
modules that are smart enough to call the right tool. |
40 |
|
41 |
Is there actually a decent systemd-based rescue CD out there? |
42 |
|
43 |
-- |
44 |
Rich |