On Friday 28 September 2001 21.42, Michael Hasenstein wrote:
Anders Johansson wrote:
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.
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?
So what do you want now? This is a direct contradiction of yourself. In the first mail you say you want it run after the scripts, and now you say before???
Apart from that this is the wrong way to do it (ok, that's half religion). Just put your driver in /etc/rc.config variable INITRD_MODULES, run mk_initrd;lilo (I hope you still have the default SuSE kernel and initrd system and didn't create your own system and kernel that don't support this and have different filenames), and that's it.
Or, add an alias for the module in /etc/modules.conf if it's not needed to mount the root-fs. This is sufficient, the kernel will autoload the module on demand.
No, it wasn't I who wanted it run after, it was the original poster. I'm quite happy with the way things are, I just tried to answer the poster. I'm also aware of the other methods of loading the kernels, I just put it there because I was trying several things to see what worked, the trial-and-error method, and when I finally found the right module, I just haven't gotten around to 'cleaning it up' My mail wasn't a critique of SuSE, my other mails to this list should have made it clear that I'm a great supporter of your work. Again, I was just trying to provide an answer to the original poster. Sorry if I upset anyone best regards Anders