Anders Johansson wrote:
On Friday 28 September 2001 21.19, Michael Hasenstein wrote:
Anders Johansson wrote:
On Friday 28 September 2001 20.09, Michael Hasenstein wrote:
Anders Johansson wrote:
I don't believe there is such a script in suse. The bootup runlevel sequence is controlled by the script /etc/rc.d/rc. If you want to run something after all the scripts in the runlevel have been run, I suggest you append it to the end of that.
So what is boot.local for... it seems some people just don't look very hard before coming to conclusions. Of course SuSE sees the need for a "local" script as well.
I looked a bit harder than you, apparently. boot.local is run *before* the rc scripts. The question was for a script that was run after.
Apparently you did not.
Not on my SuSE Linux 7.2 system, and also not on my SL7.1 system. No idea what you are using. In both the boot.local call is clearly AFTER the runlevel scripts are run.
Again: look harder!
Michael
In my boot.local script I modprobe my scsi drivers, used to power my hard drive. This hard drive is then the source of programs started in rc.d-scripts. How is this possible if it's run after rc-scripts?
Also, I quote from /etc/rc.d/boot.local
# Here you should add things, that should happen directly after booting # before we're going to the first run level.
Note "BEFORE we're going..."
How hard do I have to look?
Just read /etc/rc.d/boot. Read the SOURCE and not comments to find out facts.