[HEADS-UP] systemd for F14 - the next steps

[drago01]

On Wed, Jul 14, 2010 at 8:24 PM, Jeff Garzik <jgarzik at pobox.com> wrote:
> On 07/14/2010 02:13 PM, Lennart Poettering wrote:
>> On Wed, 14.07.10 13:44, Bill Nottingham (notting at redhat.com) wrote:
>>
>>>
>>> Lennart Poettering (mzerqung at 0pointer.de) said:
>>>> There's also the systemd.unit= kernel command line option which you may
>>>> use to boot into different targets. See the feature page for details.
>>>
>>> Does it pull this from inittab if there's no other configuration for
>>> this?
>>
>> Ok. You got me on this one. Systemd does actually not parse the
>> inittab. That cruft looked a bit too ugly and clumsy and old for us to
>> support.
>>
>> However, we have added replcacements for everything is was used
>> for. i.e. the gettys are started now via normal services.
>>
>> The replacement for the default runlevel stuff is a symlink in
>> /etc/systemd/system. You could do this:
>>
>> /etc/systemd/system/default.target → /lib/systemd/system/multi-user.target
>>
>> to avoid the graphical UI, and boot into the text console only
>> (i.e. much like the old runlevel 3)
>>
>> Or you could do this:
>>
>> /etc/systemd/system/default.target → /lib/systemd/system/graphical.target
>>
>> to boot into the graphical stuff by default. This is the default as we
>> package it.
>
> Or you could just parse inittab and notice when runlevel 3 was listed.
> Keeps everything nice and compatible, including existing manuals and
> books, and sysadmin knowledge.

What about the passing a runlevel number to the kernel cmdline?

(Thats what I use when I want a different runlevel and not fiddle with
random config files).