On 01/28/2014 03:39 AM, Guillem Jover wrote:
> Option D
> 
> * Switch to sysvinit + OpenRC wherever available.
>   - architectures where OpenRC is not currently available will switch
>     whenever OpenRC has been ported, retaining their current default
>     in the meantime.
>   - a reimplementation of OpenRC, providing the same interfaces to
>     the wider system, would satisfy the criteria above.

I'm bothered by this phrasing. The "wherever available" doesn't sound
appropriate to me.

This shows that the writer didn't have all the information in his hands
when writing this text. So I think I should explain what's the current
status of OpenRC and ports.

1/ kFreeBSD
For kFreeBSD, it "just works" (minus some warnings about stuff not being
mounted very very early in the boot which we'd have to investigate,
though it doesn't seem so bad and even impacting at all, and my
virtualbox VM just boots fine...).

2/ Hurd
For Hurd itself, it needs some fixes to be uploaded in sysvinit. It's
not well known, but Hurd doesn't support *any* init system at all right
now, it's only in the process of doing so. I wonder why it's taking so
long to have the patches applied by the way (it's been waiting in the
BTS since early September 2013).

So Hurd *will* support sysv-rc & OpenRC *soon* if someone decides to fix
sysvinit. Though OpenRC in Hurd itself is ok already. See #721917 if you
want to know more.

Once that bug is fixed, then we just need #736636 to be solved (with the
attached patch). Since #721917 is blocking, and that it's taking so long
to have things to move, I'm not in such a hurry to have the new patch in
#736636 uploaded (the bug committer just got his access on the new
OpenRC project on Alioth and will do the work by himself).

3/ Conclusion
So, all together, I think it's reasonable to say that *we do* have
OpenRC support on all platforms, and that it's only a mater of closing a
few RC bugs with attached patches (so, nothing blocking).

Hoping that this will help others to understand better what's going on
and know what we are at today.

Cheers,

Thomas


-- 
To UNSUBSCRIBE, email to debian-vote-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52e7d07a.3030...@debian.org

Reply via email to