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

Re: Switching the default startup method

[Andreas Barth]
> Hi Petter,

Hi, and sorry for the late reply.  With a kid in the house, I have so
little free time to spend on Debian, and ended up focusing on trying
to fix the issues you brought up instead of spending the time to write
a proper reply to you first.

> I appreciate that you're working on improving the experience of our
> users during startup, e.g. by adding dependency information to the
> init scripts. I think that will in the long run be good for Debians
> users.

Thank you.

> For this reason I propose that you undo the dependency, and keep on
> maintaining and improving insserv, and convincing people by the good
> quality of the package and its usefulness to install it (instead of
> forcing it on the people by a hard depends).

This migration is done to fix some long standing bugs in the boot
system, which has previously been very hard or impossible to fix
properly with the API using static sequence numbers provided by
update-rc.d.  The work to update init.d headers have been going on for
around 5 years, and a lot of people have been using this flawlessly
for several years.  Most scripts have correct or good enough
dependency information, and the few ones that do not are buggy and
need to be fixed.  This is part of the reason the boot system team
believe swithcing now was the right thing to do, to ensure that any
remaining problems can found and fixed in time for Squeeze.  It is
time to get rid of the ordering bugs in the boot system, and switch to
a mechanism that will give a robust and correct boot and shutdown
sequence for the future.

As you probably already saw in the boot system announcement[1] the
boot system team have been working on, and finally managed to publish
this weeked, the migration path has been changed a bit, to make it
easier to postpone the migration and move the responsibility of
tracking if the migration is done or not to the sysv-rc package were
it belong.  Earlier, the debconf question was priority medium, while
now it is critical.  Not changing the debconf priority before changing
the default to dependency based boot sequencing was a mistake on my
part.  Errors blocking migration are now shown using a debconf
template, and the wiki documentation[2] have been updated to help out
with migration problems.  We will follow any reported issues closely,
and continue to spend our time on the issues to make this transition
as smooth as possible.

  1 http://lists.debian.org/debian-devel-announce/2009/09/msg00003.html
  2 http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot

Happy hacking,
Petter Reinholdtsen

Reply to: