On Fri, 2004-01-02 at 04:50, Mark Gray wrote:
John Andersen
writes: On Thursday 01 January 2004 18:41, Chuck Stuettgen wrote:
So if anyone has any more suggestions I would like to hear them. =A0In the mean time I think I'm going to send a message to Werner Fink at Suse the author of insserv and see what his thoughts are.
Run insserv -d and see what it does to your configuration. I think you will find it gets set back. Somewhere in the process this will get run and when you least expect it your system reverts to that which the scripts define by thier "required start" and "provides" lines.
insserv.conf (i think thats the name) gets involved too. There is definitly some bit missing from the docs. I'd be interested in what Werner says. I note that Mantel had a hand in some of these things as well.
The problem is caused by the syslog dependency -- if you either remove $network from syslog, or $syslog from pcmcia then insserv -d will obey the network's 'Required-Start: $pcmcia' line.
(If you do remove $network from syslog you will probably have to replace it with $local_fs however.)
That was the trick.
Having said this - you should be aware that it appears there is a
dependency between when you run insserv -d and the order of the entries
in the init files.
On my test laptop, (Inspiron 4000), I removed both network entries from
syslog and added $local_fs to the Required-Start: line. I left the
Required-Stop: line blank.
Then I removed both network and hotplug entries from PCMCIA. When I ran
insserv I got the following start order.
S01pcmcia
S01random
S01syslog
S03resmgr
S05network
S06hotplug
S08portmap
S08smbfs
S08splash_early
S12acpid
S12alsasound
S12fbset
S12sshd
S13cpufreqd
S13cups
S13kbd
S13splash
S14cron
S14hwscan
S14nscd
S15splash_late
S15xdm
As you can see I PCMCIA starts first. When I duplicated the same edits
on my Latitude laptop I got several warnings and a different order. I
added the hotplug entry back in the PCMCIA script then ran insserv I
still got warnings. I then added the network entry back to PCMCIA but
put it after hotplug and ran insserv again. This time I did not get any
errors or warnings and PCMCIA the first service to start.
So to recap this is what I had to do to get PCMCIA to start first on my
Latitude laptop.
I removed both network entries from syslog and added $local_fs to the
Required-Start: line. I left the Required-Stop: line blank.
I also changed the order of the X-UnitedLinux-Should-Start: line in
pcmcia. I reversed the of network and hotplug to hotplug network.
When I ran insserv -d it results in the following start order in rc5.d:
S01pcmcia
S01random
S01syslog
S02hotplug
S03resmgr
S05network
S05portmap
S05splash_early
S06smbfs
S09acpid
S09alsasound
S09fbset
S09sshd
S10cpufreqd
S10cups
S10kbd
S10splash
S11hwscan
S11smpppd
S12xdm
S13cron
S13nscd
S14splash_late
* * *
To summarize you just have to experiment. But make one change at a time
and run insserv between each change.
Thanks to every one who posted and especially John Anderson and Mark
Gray.
Now all we have to worry about is SuSE updating the init scripts. :-)
--
Chuck Stuettgen