pk wrote:
> J.O. Aho wrote:
>
>> It shouldn't be too difficult to do that
>>
>> ln -sfn /etc/runlevels /etc/rc.d
>> mkdir -p /etc/rc.d
>> ln -sfn /etc/runlevels/1 /etc/rc.d/rc1.d
>> ln -sfn /etc/runlevels/1 /etc/rc.d/rc2.d
>> ln -sfn /etc/runlevels/1 /etc/rc.d/rc3.d
>> ln -sfn /etc/runlevels/1 /etc/rc.d/rc4.d
>> ln -sfn /etc/runlevels/1 /etc/rc.d/rc5.d
>> mkdir -p /etc/runlevels/1
>> mkdir -p /etc/runlevels/2
>> mkdir -p /etc/runlevels/3
>> mkdir -p /etc/runlevels/4
>> mkdir -p /etc/runlevels/5
>>
>>
>> replace in /etc/inittab:
>> l1:S1:wait:/sbin/rc single
>> l2:2:wait:/sbin/rc default
>> l3:3:wait:/sbin/rc default
>> l4:4:wait:/sbin/rc default
>> l5:5:wait:/sbin/rc default
>>
>> to:
>> l1:S1:wait:/sbin/rc 1
>> l2:2:wait:/sbin/rc 2
>> l3:3:wait:/sbin/rc 3
>> l4:4:wait:/sbin/rc 4
>> l5:5:wait:/sbin/rc 5
>>
>> Just don't forget to update the runlevels to contain the right service
>> symlinks.
>
> Wouldn't all of this be blown away at the first baselayout update? You'll
> have to be careful to not let portage overwrite the files you modified.
>

No, inittab is protected by default, you will get opted if you want to update
it or not, and you can always protect it more permanently in make.conf.
Upgrading baselayout won't affect anything else.

--

//Aho

J.O. Aho wrote:

> No, inittab is protected by default, you will get opted if you want to
> update it or not, and you can always protect it more permanently in
> make.conf.

Protecting a file only means it's not automatically overwritten, but as long
as portage sees the ._cfg* files it will keep asking (through etc-update or
similar tools) whether you want to overwrite it. Not saying that you can't
do that, of course, but you still have to be careful, especially if
etc-update tells you that 144 files need to be updated, /etc/inittab is
among those, and you don't notice that (I'm speaking out of direct
experience, btw; I once unthinkingly replaced my customized inittab with
the default one. Luckily I had a backup :-)).