* Jon Dowland
| On Wed, Aug 24, 2005 at 08:52:36AM +0200, Tollef Fog Heen wrote:
| If you have an USB mouse, you need to have the driver for it loaded
| before starting gdm (or the boot will fail), if it uses Xdmcp for
| connecting to a terminal server, it will need networking to be up (and
|
On Thu, Aug 25, 2005 at 09:34:18AM +0200, Tollef Fog Heen wrote:
Well, it was an example. Another example involving X would be if you
use a font server.
Other examples could be ppp, which on my system would have to wait
until fcdsl is loaded, while on other systems might wait for setserial
* Petter Reinholdtsen
| Add a block like this in the init.d script (example based on
| xdebconfigurator):
|
| ### BEGIN INIT INFO
| # Provides: xdebconfigurator
| # Required-Start:$syslog
| # Required-Stop: $syslog
| # Should-Start: $local_fs
| # Should-Stop:
[Tollef Fog Heen]
This doesn't handle the case of dynamic dependencies:
That is correct. So to handle those, one need to support override
files loaded from somewhere else. This also make it possible to add
dependency info for scripts currently missing it.
I got a sketch package working as a
On Mon, 22 Aug 2005 13:21:19 +0200, Petter Reinholdtsen
[EMAIL PROTECTED] wrote:
On Mon, Aug 22, 2005 at 12:59:49PM +0200, Marc Haber wrote:
How about a recipe for doing so?
Good idea. Here is a quick and dirty draft based on my current
understanding.
http://wiki.debian.net/?LSBInitScripts
On Wed, Aug 24, 2005 at 08:52:36AM +0200, Tollef Fog Heen wrote:
If you have an USB mouse, you need to have the driver for it loaded
before starting gdm (or the boot will fail), if it uses Xdmcp for
connecting to a terminal server, it will need networking to be up (and
so on).
This is the net
[Marcelo E. Magallon]
Isn't just:
wait
enough?
In this case, yes. In the general case, it is unknown if a background
process was forked off earlier in the script, so you want to control
which processes to wait for.
I suspect 'wait $pid || true' or similar is needed though, as the
[Martin F Krafft]
The place to discuss issues like this would be the initscripts-ng
project on alioth. There's a mailing list...
Good idea. I'll head over there. :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Marco d'Itri]
I'm sure that a fair number of critical scripts (e.g. some dealing
with networking) are not.
Yeah, me too. I've seen incorrect init.d ordering several times. And
to be able to detect and fix incorrect boot order, we need to know
dependencies. I hope as many as possible will
On Mon, 22 Aug 2005, Petter Reinholdtsen wrote:
my packages. After all, it can not hurt to document expectations, and
the headers can be used by any implementation so it is not tied to a
given approach.
No, they cannot. But they are a good starting point, so go ahead.
If you want me to
On Mon, 22 Aug 2005 09:32:48 +0200, Petter Reinholdtsen
[EMAIL PROTECTED] wrote:
Yeah, me too. I've seen incorrect init.d ordering several times. And
to be able to detect and fix incorrect boot order, we need to know
dependencies. I hope as many as possible will add dependency
information using
On Mon, Aug 22, 2005 at 12:59:49PM +0200, Marc Haber wrote:
On Mon, 22 Aug 2005 09:32:48 +0200, Petter Reinholdtsen
[EMAIL PROTECTED] wrote:
Yeah, me too. I've seen incorrect init.d ordering several times. And
to be able to detect and fix incorrect boot order, we need to know
dependencies.
Recently, I have been investigating how to speed up the boot process
in Debian, and during this work, I found a simple way to change
/etc/init.d/rc to run all init.d scripts with the same sequence number
in parallell. Patch included below. For this change to work as it
should, we need to make
also sprach Petter Reinholdtsen [EMAIL PROTECTED] [2005.08.22.0113 +0200]:
Any comments on this approach?
The place to discuss issues like this would be the initscripts-ng
project on alioth. There's a mailing list...
--
Please do not send copies of list mail to me; I read the list!
.''`.
On Aug 22, Petter Reinholdtsen [EMAIL PROTECTED] wrote:
in parallell. Patch included below. For this change to work as it
should, we need to make sure init.d-scripts are ordered according to
dependency, so scripts needed by other scripts get a earlier sequence
number. And to make it
On Mon, Aug 22, 2005 at 01:13:08AM +0200, Petter Reinholdtsen wrote:
+for pid in $pids ; do
+wait $pid
+done
Isn't just:
wait
enough?
--
Marcelo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
16 matches
Mail list logo
