[gentoo-dev] New basic systemd profile

[gentoo-dev] New basic systemd profile

[Mike Gilbert]

Due to popular demand, I have added a basic systemd profile for amd64:

default/linux/amd64/13.0/systemd

Previously, the systemd profile was only available in combination with
gnome or kde. This new profile will make it easier for users to switch
to systemd from an unpacked stage3 tarball.

To avoid an explosion in profiles, I will not be adding this for other
archs at this time. I'm not opposed to it, but I also don't want to be
responsible for making repoman that much slower.

Re: [gentoo-dev] New basic systemd profile

[Andrew Udvare]

> On 2015-05-01, at 08:28, Mike Gilbert <floppym@gentoo.org> wrote:
> 
> Due to popular demand, I have added a basic systemd profile for amd64:
> 
> default/linux/amd64/13.0/systemd
> 
> Previously, the systemd profile was only available in combination with
> gnome or kde. This new profile will make it easier for users to switch
> to systemd from an unpacked stage3 tarball.
> 
> To avoid an explosion in profiles, I will not be adding this for other
> archs at this time. I'm not opposed to it, but I also don't want to be
> responsible for making repoman that much slower.
> 

I would like to see a hardened version of this. Making a hardened Gentoo kernel (there is no 'systemd' option in hardened-sources menuconfig) and system with systemd is almost entirely undocumented. I managed to do it though.

Re: [gentoo-dev] New basic systemd profile

[Mike Gilbert]

On Fri, May 1, 2015 at 11:44 AM, Andrew Udvare <audvare@gmail.com> wrote:
>
>> On 2015-05-01, at 08:28, Mike Gilbert <floppym@gentoo.org> wrote:
>>
>> Due to popular demand, I have added a basic systemd profile for amd64:
>>
>> default/linux/amd64/13.0/systemd
>>
>> Previously, the systemd profile was only available in combination with
>> gnome or kde. This new profile will make it easier for users to switch
>> to systemd from an unpacked stage3 tarball.
>>
>> To avoid an explosion in profiles, I will not be adding this for other
>> archs at this time. I'm not opposed to it, but I also don't want to be
>> responsible for making repoman that much slower.
>>
>
> I would like to see a hardened version of this. Making a hardened Gentoo kernel (there is no 'systemd' option in hardened-sources menuconfig) and system with systemd is almost entirely undocumented. I managed to do it though.

I will leave this to the hardened team to implement a systemd profile
if they wish.

As for documentation on building a kernel: The systemd ebuild has a
list of suggested options in the CONFIG_CHECK variable in pkg_pretend.
The systemd ebuild will warn you if your kernel config is missing any
options.

Re: [gentoo-dev] New basic systemd profile

[Alexis Ballier]

On Fri, 1 May 2015 11:28:52 -0400
Mike Gilbert <floppym@gentoo.org> wrote:

> Due to popular demand, I have added a basic systemd profile for amd64:

what about we start telling people /etc/make.profile can be a dir
and that you can fill the 'parent' file in there just as well as you ln
-s it ?

Alexis.

Re: [gentoo-dev] New basic systemd profile

[Rich Freeman]

On Sat, May 2, 2015 at 4:20 AM, Alexis Ballier <aballier@gentoo.org> wrote:
> On Fri, 1 May 2015 11:28:52 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
>
>> Due to popular demand, I have added a basic systemd profile for amd64:
>
> what about we start telling people /etc/make.profile can be a dir
> and that you can fill the 'parent' file in there just as well as you ln
> -s it ?

That is the whole mix-in concept.  In order to make that work we'd
really need to work towards it.  You can't inherit profiles in
arbitrary order.  If you want something like mix-ins you really need
to split profiles up into certain classes and define rules about which
ones are used for what.  Then they won't be stepping on each other's
toes.

But yes, you could probably get away with it in many cases without any
special support from the distro.

-- 
Rich

Re: [gentoo-dev] New basic systemd profile

[Alexis Ballier]

On Sat, 2 May 2015 05:53:57 -0400
Rich Freeman <rich0@gentoo.org> wrote:

> On Sat, May 2, 2015 at 4:20 AM, Alexis Ballier <aballier@gentoo.org>
> wrote:
> > On Fri, 1 May 2015 11:28:52 -0400
> > Mike Gilbert <floppym@gentoo.org> wrote:
> >
> >> Due to popular demand, I have added a basic systemd profile for
> >> amd64:
> >
> > what about we start telling people /etc/make.profile can be a dir
> > and that you can fill the 'parent' file in there just as well as
> > you ln -s it ?
> 
> That is the whole mix-in concept.  In order to make that work we'd
> really need to work towards it.  You can't inherit profiles in
> arbitrary order.  If you want something like mix-ins you really need
> to split profiles up into certain classes and define rules about which
> ones are used for what.  Then they won't be stepping on each other's
> toes.


Rules that make that work are simple, but instead, we seem to be heading
towards '# of arches * # of DEs * # of init systems * # of gentoo
releases * # of ABIs * # of libcs' profiles. Most of them being just
about a 'parent' file, and thus, I hope, following the good practices :)

Alexis.

Re: [gentoo-dev] New basic systemd profile

[Mike Gilbert]

On Sat, May 2, 2015 at 11:26 AM, Alexis Ballier <aballier@gentoo.org> wrote:
> On Sat, 2 May 2015 05:53:57 -0400
> Rich Freeman <rich0@gentoo.org> wrote:
>
>> On Sat, May 2, 2015 at 4:20 AM, Alexis Ballier <aballier@gentoo.org>
>> wrote:
>> > On Fri, 1 May 2015 11:28:52 -0400
>> > Mike Gilbert <floppym@gentoo.org> wrote:
>> >
>> >> Due to popular demand, I have added a basic systemd profile for
>> >> amd64:
>> >
>> > what about we start telling people /etc/make.profile can be a dir
>> > and that you can fill the 'parent' file in there just as well as
>> > you ln -s it ?
>>
>> That is the whole mix-in concept.  In order to make that work we'd
>> really need to work towards it.  You can't inherit profiles in
>> arbitrary order.  If you want something like mix-ins you really need
>> to split profiles up into certain classes and define rules about which
>> ones are used for what.  Then they won't be stepping on each other's
>> toes.
>
>
> Rules that make that work are simple, but instead, we seem to be heading
> towards '# of arches * # of DEs * # of init systems * # of gentoo
> releases * # of ABIs * # of libcs' profiles. Most of them being just
> about a 'parent' file, and thus, I hope, following the good practices :)
>

Someone needs to do the work of writing the rules down.

Also, repoman probably needs to be adjusted so that we actually test
some useful subset of the possible combinations. There's no such
support today.