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

[drago01]

On Wed, Jul 14, 2010 at 7:01 PM, Bill Nottingham <notting at redhat.com> wrote:
> Lennart Poettering (mzerqung at 0pointer.de) said:
>> Well, I don't think we want to support both. I believe F14 should be
>> systemd and only systemd, but we want the option to revert to upstart
>> should that not work out.
>>
>> I am very much interested to get upgraded systems to use systemd as
>> well, which is why I'd really like to go the Obsoletes way, and use a
>> versioned Obsoletes, so that we can switch back to upstart if we want to
>> by another versioned Obsoletes, but this time from upstart. (which is
>> exactly what James Antill proposed in his mail)
>>
>> Or in other words: I'd like to make this switch for the whole distro,
>> not leave it to the individual machines.
>>
>> So, unless there is really strong opposition to the Obsoletes approach
>> I'd go on and do the switch?
>
> If we're at the... 95% coverage case, I guess. What I don't want is that
> machines suddenly stop booting with no recourse other than init=/bin/bash
> and manual recovery. There are some side cases that would be nice to either
> have working, or documenting that they're not done yet (serial consoles,
> assorted other things.)

What about this (ugly) approach:

Make upstart require systemd and make it to be the default.
This was people running "yum update" will get systemd while still
having upstart as a fallback in case stuff breaks.

Once we decide to stick to it we could remove the requirement and add
the obsolete.