[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#727708: tech-ctte: Decide which init system to default to in Debian.

On Mon, 2013-10-28 at 19:38 -0700, Russ Allbery wrote:
> Brian May <brian@microcomaustralia.com.au> writes:
> > On 29 October 2013 12:21, Russ Allbery <rra@debian.org> wrote:
> >> In other words, I don't think it would make any sense at all to
> >> standardize on upstart or systemd and then ask people to continue to
> >> write init scripts in the long run (transition issues aside).  Getting
> >> rid of init scripts is not the whole point, but it's a huge part of it.
> > My understanding is that init scripts will still be required for FreeBSD
> > and The Hurd.
> I would not assume that.  At least, I personally don't think that
> switching to upstart or systemd as a default but requiring that everyone
> provide both files for that system and init scripts for Hurd and kFreeBSD
> to be a good outcome, since I don't think that will be something at which
> Debian will be successful.
> There are various other options, including not changing away from sysvinit
> or someone porting the necessary support to Hurd and kFreeBSD.  Or, of
> course, dropping Hurd and kFreeBSD, although I'm sure that no one wants
> that outcome.

I do.  I think non-Linux ports make more sense as derivative
distributions.  This gives them the freedom to drop packages that aren't
worth porting, work around Linux-isms as necessary, improve integration
with their own kernel, and release on their own schedule - rather than
trying to make all the crap in Debian build.  (Remember, 90% of
everything is crap.)


Ben Hutchings
[W]e found...that it wasn't as easy to get programs right as we had thought.
... I realized that a large part of my life from then on was going to be spent
in finding mistakes in my own programs. - Maurice Wilkes, 1949

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: