[HEADS-UP] systemd is now the default init system in rawhide

[Peter Jones]

On 07/26/2010 10:33 PM, Adam Williamson wrote:
> On Mon, 2010-07-26 at 11:32 -0400, Peter Jones wrote:
>> On 07/25/2010 04:30 AM, Frank Murphy wrote:
>>> On 25/07/10 07:34, Kevin Fenzi wrote:
>>>> Greetings.
>>>>
>>>> first it seems that systemd-sysvinit needs to add a:
>>>>
>>>> Provides: sysvinit-userspace
>>>>
>>>> To avoid the current conflicts/upgrade problems:
>>>>
>>>> --->  Package upstart-sysvinit.x86_64 0:0.6.5-7.fc14 set to be installed
>>>> -->  Processing Conflict: upstart-sysvinit-0.6.5-7.fc14.x86_64 conflicts systemd-sysvinit
>>>> -->  Processing Conflict: systemd-sysvinit-4-3.fc14.x86_64 conflicts upstart-sysvinit
>>>> Error: systemd-sysvinit conflicts with upstart-sysvinit
>>>
>>> thank Seth? for yum --exclude=systemd\*
>>>
>>> Will  systemd be default in F14-Branched,
>>> or be kept with devel?
>>
>> As of yet, that's still undecided.
> 
> That doesn't sound right. AIUI, the situation is that systemd will be
> default for F-14 unless we find it to be horribly broken, hence it will
> become the default in F14-Branched when it branches (unless we've
> already decided it's horribly broken by then, which doesn't seem
> likely).

If you consult http://meetbot.fedoraproject.org/meetbot/fedora-meeting/2010-06-15/fesco.2010-06-15-19.35.log.html ,
you'll see that what FESCo agreed on was that it was a desirable feature, and that
we would revisit the question of being default in F-14 later, when there's more
actual data.

That being said, I expect it will remain default in the branch for at least some
amount of time for the same reason, and because that's the default state if nobody
specifically changes it.

-- 
        Peter

In computing, turning the obvious into the useful is a living
definition of the word "frustration"
		-- Alan Perlis

01234567890123456789012345678901234567890123456789012345678901234567890123456789