This one time, at band camp, Petter Reinholdtsen said:
Package: hdparm
Version: 6.1-7
Severity: wishlist
To be able to check boot script order, and also to be able to start
boot scripts in parallel, it is important to know the dependencies of
the various boot scripts. The Linux
[Stephen Gran]
Default-Start should really only be S, except that if a device node
is created by udev or something later, it will run again for that
device node. I do not know if that makes a difference in this
setup, though.
You probably know best. It does not make much difference in this
This one time, at band camp, Petter Reinholdtsen said:
[Stephen Gran]
Default-Start should really only be S, except that if a device node
is created by udev or something later, it will run again for that
device node. I do not know if that makes a difference in this
setup, though.
You
This one time, at band camp, Petter Reinholdtsen said:
[Stephen Gran]
Default-Start should really only be S, except that if a device node
is created by udev or something later, it will run again for that
device node. I do not know if that makes a difference in this
setup, though.
You
[Stephen Gran]
Now, one thing that has been bothering me - is there a facility in
these scripts to sya, 'wait until all scripts of type foo are done
to start, if present'? In other words, something like a
Should-Start-Group: with the other scripts useing a Member-Of:
rather than a Provides:
This one time, at band camp, Petter Reinholdtsen said:
[Stephen Gran]
Now, one thing that has been bothering me - is there a facility in
these scripts to sya, 'wait until all scripts of type foo are done
to start, if present'? In other words, something like a
Should-Start-Group: with the
Package: hdparm
Version: 6.1-7
Severity: wishlist
To be able to check boot script order, and also to be able to start
boot scripts in parallel, it is important to know the dependencies of
the various boot scripts. The Linux Software Base specifies a init.d
header file format useful for this
7 matches
Mail list logo
