[Pkg-sysvinit-devel] Initscripts presentation
Henrique de Moraes Holschuh
hmh at debian.org
Fri Jan 6 16:51:57 UTC 2006
On Fri, 06 Jan 2006, Petter Reinholdtsen wrote:
> [Henrique de Moraes Holschuh]
> > And init-ng _definately_ is the way to go nowadays (or write one
> > from scratch).
> Why? I fail to see why we need to drop the current init.d scripts and
No dropping of init.d scripts. That would be stupid, scripts are too good
to do without, all other solutions based in buzzwords I've seen so far are
not nearly as good, although some have their appeal.
In fact, back in 2002 I was already talking about doing it and keeping the
init.d initscripts (I call them sysv initscripts).
> move to a different format, when it is possible to get both dependency
> handling and parallell execution with sysvinit.
What you call parallel execution with sysvinit is not parallel execution
with sysv-rc. Most of the time, you can not be really sure what people are
talking about :) And yes, it is possible to do proper parallel execution
using sysv init plus a lot of external stuff. But tacking a full
dependency-based system on top of sysv init ain't a good idea unless init
itself is extended for some extra functionality.
But this thread is off-topic here, join the ML for the initscripts-ng
project in Alioth and read the archives.
Whatever init-ng is _now_ is probably quite not enough for Debian, but it is
a good base to prototype on last time I checked.
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
More information about the Pkg-sysvinit-devel