I need to change the boot sequence for SuSE8.0 on my laptop. It insists on trying to initialize eth0 before PCMCIA. Of course this fails. I can manually restart the network driver, and eth0 will work normally, but this is a bad solution. So... this leads into my question. How do I change the boot sequence so that PCMCIA is initialized first, and then it searches for and turns on eth0? Is there a good resource for info on the boot sequence? I haven't been able to find anything really helpful yet. C.
On donderdag 23 mei 2002 06:31, Clayton Cornell wrote:
I need to change the boot sequence for SuSE8.0 on my laptop. It insists on trying to initialize eth0 before PCMCIA. Of course this fails. I can manually restart the network driver, and eth0 will work normally, but this is a bad solution.
So... this leads into my question. How do I change the boot sequence so that PCMCIA is initialized first, and then it searches for and turns on eth0?
Is there a good resource for info on the boot sequence? I haven't been able to find anything really helpful yet.
C.
Change the file names in: /etc/init.d/rc5.d -- Richard Bos Democracy cost a fortune
Boot sequences are set up by symlinks in the per-run level directories: /etc/init.d/rcn.d where n corresponds to run level. on my laptop, in /etc/init.d/rc5.d: S08pcmcia is a symlink to ../pcmcia. The /etc/init.d/rc script will execute the scripts in order. First it executes the Kxx scripts, then the Sxx scripts: for i in rc5.d/S[0-9][0-9]*; do #Then it tests to determine if the script actually exits and is executable. test -x $i || continue The Snn script is then processed. On 23 May 2002 at 6:31, Clayton Cornell wrote:
I need to change the boot sequence for SuSE8.0 on my laptop. It insists on trying to initialize eth0 before PCMCIA. Of course this fails. I can manually restart the network driver, and eth0 will work normally, but this is a bad solution.
So... this leads into my question. How do I change the boot sequence so that PCMCIA is initialized first, and then it searches for and turns on eth0?
Is there a good resource for info on the boot sequence? I haven't been able to find anything really helpful yet.
C.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Jerry Feldman Enterprise Systems Group Hewlett-Packard Company 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752 508-467-4315 http://www.testdrive.compaq.com/linux/
On Thursday 23 May 2002 16.06, Jerry Feldman wrote:
Boot sequences are set up by symlinks in the per-run level directories: /etc/init.d/rcn.d where n corresponds to run level. on my laptop, in /etc/init.d/rc5.d: S08pcmcia is a symlink to ../pcmcia. The /etc/init.d/rc script will execute the scripts in order. First it executes the Kxx scripts, then the Sxx scripts: for i in rc5.d/S[0-9][0-9]*; do #Then it tests to determine if the script actually exits and is executable. test -x $i || continue
The Snn script is then processed.
Not quite. The K* scripts are run if you leave the runlevel, not when you enter it. In /etc/init.d/rc you have for i in $prerc/K${rex}*; do note the prerc. Also, it's not executed at all if there's a S* script for the same service in the new runlevel. However, to change the order of the scripts, I'd suggest adding network to the "Required-start" line in /etc/init.d/pcmcia. Then run "insserv -r pcmcia" follwed by "insserv -d pcmcia". That should fix the order of execution. regards Anders -- I swear I do declare - how did you get that there?
Thanks... this is exactly what I needed. Now to go mess with the laptop. and see what else I can break on it. ;-) C. On Thursday 23 May 2002 16:14, Anders Johansson wrote:
On Thursday 23 May 2002 16.06, Jerry Feldman wrote:
Boot sequences are set up by symlinks in the per-run level directories: /etc/init.d/rcn.d where n corresponds to run level. on my laptop, in /etc/init.d/rc5.d: S08pcmcia is a symlink to ../pcmcia. The /etc/init.d/rc script will execute the scripts in order. First it executes the Kxx scripts, then the Sxx scripts: for i in rc5.d/S[0-9][0-9]*; do #Then it tests to determine if the script actually exits and is executable. test -x $i || continue
The Snn script is then processed.
Not quite. The K* scripts are run if you leave the runlevel, not when you enter it. In /etc/init.d/rc you have
for i in $prerc/K${rex}*; do
note the prerc. Also, it's not executed at all if there's a S* script for the same service in the new runlevel.
However, to change the order of the scripts, I'd suggest adding network to the "Required-start" line in /etc/init.d/pcmcia. Then run "insserv -r pcmcia" follwed by "insserv -d pcmcia". That should fix the order of execution.
regards Anders
participants (4)
-
Anders Johansson
-
Clayton Cornell
-
Jerry Feldman
-
Richard Bos