Please help me make athcool compatible with dependency-based init systems (was: Release Update: freeze, architecture requalification)

[Nicolas Boullis]

Hi,

Disclaimer: I've been pretty busy recently, not giving my Debian
packages the care and love they deserve. That's why I'm now asking for
help, somewhat late...

On Sat, Jul 19, 2008 at 03:35:35PM +0200, Luk Claes wrote:
>
> * Prepare init.d-Scripts for dependency-based init systems
>
> Wider testing of dependency-based init systems has lead to some new bugs
> for this goal, but the current state looks quite well. We are confident
> that we will have full support for dep-based init system in lenny.

One of my packages, namely athcool installs an init script that is not
yet compatible with dependency-based init systems. For some reason, it
was not detected by automatic systems such as lintian, and no bug was
filed against it, and no-one cared about it yet.

Athcool installs an init script but does not install links to run it on
boot, and that might be the reason why lintian did not notice about it.
(No startup link is installed because athcool causes bad stability
issues on some systems. If one tests it and experiences such problems,
the system is back to a normal state after a reboot.) Someone who is
satisfied with athcool can run update-rc.d (as documented in
/usr/share/doc/athcool/README.Debian) to enable startup links.

I'd like to reproduce a similar behaviour with the headers for
dependency-based init systems, but I know close to nothing about such
systems. I read the corresponding section of the LSB, but it did not
help me much. I guess I could set Default-Start and Default-Stop empty.
But then I have no idea how I would document the enablement of startup
links by the user. Since those keywords are called "Default", I guess
there is a way to override them, but how? Or I think one might change
the Default-Start and Default-Stop keyworks, but then who would they ask
the system to take the change into account?

Any help is welcome, especially as a patch or a NMU, but please don't
forget the documentation issue.


Thanks in advance,

Nicolas


PS: I have no time to read d-devel; please CC replies to me.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Nicolas Boullis]

Hi,

As a follow-up to myself, and as suggested by Kel Modderman, please also
CC replies to the developer list for initscripts-ng. (Full message kept
for those people.)


On Mon, Jul 21, 2008 at 11:33:10PM +0200, Nicolas Boullis wrote:

> Hi,
>
> Disclaimer: I've been pretty busy recently, not giving my Debian
> packages the care and love they deserve. That's why I'm now asking for
> help, somewhat late...
>
> On Sat, Jul 19, 2008 at 03:35:35PM +0200, Luk Claes wrote:
> >
> > * Prepare init.d-Scripts for dependency-based init systems
> >
> > Wider testing of dependency-based init systems has lead to some new bugs
> > for this goal, but the current state looks quite well. We are confident
> > that we will have full support for dep-based init system in lenny.
>
> One of my packages, namely athcool installs an init script that is not
> yet compatible with dependency-based init systems. For some reason, it
> was not detected by automatic systems such as lintian, and no bug was
> filed against it, and no-one cared about it yet.
>
> Athcool installs an init script but does not install links to run it on
> boot, and that might be the reason why lintian did not notice about it.
> (No startup link is installed because athcool causes bad stability
> issues on some systems. If one tests it and experiences such problems,
> the system is back to a normal state after a reboot.) Someone who is
> satisfied with athcool can run update-rc.d (as documented in
> /usr/share/doc/athcool/README.Debian) to enable startup links.
>
> I'd like to reproduce a similar behaviour with the headers for
> dependency-based init systems, but I know close to nothing about such
> systems. I read the corresponding section of the LSB, but it did not
> help me much. I guess I could set Default-Start and Default-Stop empty.
> But then I have no idea how I would document the enablement of startup
> links by the user. Since those keywords are called "Default", I guess
> there is a way to override them, but how? Or I think one might change
> the Default-Start and Default-Stop keyworks, but then who would they ask
> the system to take the change into account?
>
> Any help is welcome, especially as a patch or a NMU, but please don't
> forget the documentation issue.
>
>
> Thanks in advance,
>
> Nicolas
>
>
> PS: I have no time to read d-devel; please CC replies to me.

--
To UNSUBSCRIBE, email to debian-devel-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Kel Modderman-3]

Hi Nicolas,

On Wednesday 23 July 2008 06:18:43 Nicolas Boullis wrote:

> > Hi,
> >
> > Disclaimer: I've been pretty busy recently, not giving my Debian
> > packages the care and love they deserve. That's why I'm now asking for
> > help, somewhat late...
> >
> > On Sat, Jul 19, 2008 at 03:35:35PM +0200, Luk Claes wrote:
> > >
> > > * Prepare init.d-Scripts for dependency-based init systems
> > >
> > > Wider testing of dependency-based init systems has lead to some new bugs
> > > for this goal, but the current state looks quite well. We are confident
> > > that we will have full support for dep-based init system in lenny.
> >
> > One of my packages, namely athcool installs an init script that is not
> > yet compatible with dependency-based init systems. For some reason, it
> > was not detected by automatic systems such as lintian, and no bug was
> > filed against it, and no-one cared about it yet.
> >
> > Athcool installs an init script but does not install links to run it on
> > boot, and that might be the reason why lintian did not notice about it.
> > (No startup link is installed because athcool causes bad stability
> > issues on some systems. If one tests it and experiences such problems,
> > the system is back to a normal state after a reboot.) Someone who is
> > satisfied with athcool can run update-rc.d (as documented in
> > /usr/share/doc/athcool/README.Debian) to enable startup links.
> >
> > I'd like to reproduce a similar behaviour with the headers for
> > dependency-based init systems, but I know close to nothing about such
> > systems. I read the corresponding section of the LSB, but it did not
> > help me much. I guess I could set Default-Start and Default-Stop empty.
> > But then I have no idea how I would document the enablement of startup
> > links by the user. Since those keywords are called "Default", I guess
> > there is a way to override them, but how? Or I think one might change
> > the Default-Start and Default-Stop keyworks, but then who would they ask
> > the system to take the change into account?

Just add the LSB header with correct information like:

### BEGIN INIT INFO
# Provides:          athcool
# Required-Start:    $remote_fs
# Required-Stop:     $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:
# Description:       enable powersaving mode for Athlon/Duron processors
### END INIT INFO

Your package does not call update-rc.d in postinst, courtesy of
"dh_installinit -n", therefore no links get created even on insserv system.

There is no need to modify README.Debian instructions, as insserv package
provides an update-rc.d wrapper. When the admin follows the existing
instructions of "update-rc.d athcool start 20 2 3 4 5 ." you will get runlevel
links, just that the sequence number 20 is ignored and a more precise sequence
number is calculated by insserv.

Thanks, Kel.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Petter Reinholdtsen]

[Kel Modderman]
> There is no need to modify README.Debian instructions, as insserv
> package provides an update-rc.d wrapper. When the admin follows the
> existing instructions of "update-rc.d athcool start 20 2 3 4 5 ."
> you will get runlevel links, just that the sequence number 20 is
> ignored and a more precise sequence number is calculated by insserv.

Note that in this case the runlevels listed on the command line will
also be ignored, and the runlevels in the LSB header will be used
instead.  The effect in this case is the same.

Happy hacking,
--
Petter Reinholdtsen


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Nicolas Boullis]

Hi Kel,

On Wed, Jul 23, 2008 at 11:55:04PM +1000, Kel Modderman wrote:

> Hi Nicolas,
>
> Just add the LSB header with correct information like:
>
> ### BEGIN INIT INFO
> # Provides:          athcool
> # Required-Start:    $remote_fs
> # Required-Stop:     $remote_fs
> # Default-Start:     2 3 4 5
> # Default-Stop:
> # Description:       enable powersaving mode for Athlon/Duron processors
> ### END INIT INFO
>
> Your package does not call update-rc.d in postinst, courtesy of
> "dh_installinit -n", therefore no links get created even on insserv system.
>
> There is no need to modify README.Debian instructions, as insserv package
> provides an update-rc.d wrapper. When the admin follows the existing
> instructions of "update-rc.d athcool start 20 2 3 4 5 ." you will get runlevel
> links, just that the sequence number 20 is ignored and a more precise sequence
> number is calculated by insserv.

Thanks for your answer.
Sorry for asking a potentially stupid question, but how does the
"Default-Start" keyword affect the bahvior of the system?


Cheers,

Nicolas


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Teodor-Adrian]

On Wed, Jul 23, 2008 at 10:52 PM, Nicolas Boullis <nboullis@...> wrote:
> Sorry for asking a potentially stupid question, but how does the
> "Default-Start" keyword affect the bahvior of the system?

Refer to http://wiki.debian.org/LSBInitScripts for details. Maybe this
page should be updated for LSB 3.2?

Thanks


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Nicolas Boullis]

Hi,

On Wed, Jul 23, 2008 at 11:36:01PM +0300, Teodor wrote:
> On Wed, Jul 23, 2008 at 10:52 PM, Nicolas Boullis <nboullis@...> wrote:
> > Sorry for asking a potentially stupid question, but how does the
> > "Default-Start" keyword affect the bahvior of the system?
>
> Refer to http://wiki.debian.org/LSBInitScripts for details. Maybe this
> page should be updated for LSB 3.2?

Well... I already read LSB, but there's nothing about how it really
interacts with the system. What does "default" mean here?
Does it affect update-rc.d?
Is it used when insserv is enabled?

I'd rather be sure that no-one will get startup links unwillingly, so
I'd like to understand how it really affects things...
(For example: one installs athcool, does not create startup links and
then installs and enables insserv...)


Cheers,

Nicolas


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...