| 1 |
On 22/02/2014 18:37, Tanstaafl wrote: |
| 2 |
> On 2014-02-21 4:58 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 3 |
>> On Fri, 21 Feb 2014 09:32:07 -0500, Tanstaafl wrote: |
| 4 |
>>> Ok, so, since it really is so simple, wouldn't it be easier to |
| 5 |
>>> implement this as an eselect module then, as opposed to creating a |
| 6 |
>>> bunch of separate profiles? |
| 7 |
> |
| 8 |
>> profiles handle USE flags, eselect does not. Of course, you can use |
| 9 |
>> eselect to change profiles :) |
| 10 |
>> |
| 11 |
>> It's not as complex as creating a lot of different systemd profiles |
| 12 |
>> because of inheritance. |
| 13 |
> |
| 14 |
> Thanks Neil, but... what are you suggesting then? That it would have to |
| 15 |
> be done as profiles, but it wouldn't be really complicated? Or maybe |
| 16 |
> that it would be a combination of profile selection and... something |
| 17 |
> else (new eselect init module)? |
| 18 |
> |
| 19 |
> Remember, I want all of this to coalesce into an enhancement/feature |
| 20 |
> request for gentoo to be able to provide a sound, sane way to manage the |
| 21 |
> idea of switching init systems. |
| 22 |
|
| 23 |
eselect is not going to work and neither is a Gentoo profile. |
| 24 |
|
| 25 |
eselect manages config options between different implementation of a |
| 26 |
thing. Usually by tweaking symlinks. Switching init OpenRC <-> SystemD |
| 27 |
involves resetting uSE flags and recompiling some fundamental stuff. |
| 28 |
That exercise is unlikely to ever go into eselect. |
| 29 |
|
| 30 |
The devs on gentoo-dev already nuked the idea of a gentoo profile as |
| 31 |
such, it's not worth the effort and causes an explosion of profiles. |
| 32 |
|
| 33 |
Switching to and from systemd is a few simple steps: |
| 34 |
|
| 35 |
- Change some USE |
| 36 |
- Recompile some stuffs |
| 37 |
- maybe read a howto or two |
| 38 |
- in all likelihood reboot |
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
Conceptually, it is rather similar to switching between nouveau and |
| 43 |
nvidia. That doesn't have eselect support[1] or profiles. |
| 44 |
|
| 45 |
|
| 46 |
To switcvh to and from |
| 47 |
>>> I'd also suggest throwing in a test for current running kernel config, |
| 48 |
>>> to make sure it fully supports booting with systemd, and maybe a new |
| 49 |
>>> emerge command that can also be maintained to make sure that *all* |
| 50 |
>>> necessary packages are rebuilt? |
| 51 |
> |
| 52 |
>> That's already taken care of, the systemd ebuild checks your kernel |
| 53 |
>> config as part of the pre-emerge checks, nothing happens until you have a |
| 54 |
>> suitable kernel. |
| 55 |
> |
| 56 |
> Ok, excellent... |
| 57 |
> |
| 58 |
> |
| 59 |
> |
| 60 |
|
| 61 |
|
| 62 |
-- |
| 63 |
Alan McKinnon |
| 64 |
alan.mckinnon@×××××.com |
Archives