What is the equiv to RH /etc/rc.local? It ran after all otehr rc scripts, before the login propmt was presented? /etc/rc.d/rc.boot runs before the other init scripts, so it doesn't work. Thanks!
Hi, 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. regards Anders On Friday 28 September 2001 04.41, Timothy Reaves wrote:
What is the equiv to RH /etc/rc.local? It ran after all otehr rc scripts, before the login propmt was presented? /etc/rc.d/rc.boot runs before the other init scripts, so it doesn't work.
Thanks!
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.
On Friday 28 September 2001 7:09 pm, 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.
That would be what boot.local is for. As I recall, that's exactly what it says at the top.... _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
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. regards Anders
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
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? Anders
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.
On Friday 28 September 2001 21.39, Michael Hasenstein wrote:
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.
I have. /etc/rc.d/boot is run by init as the first thing by init. This is followed by running /etc/rc.d/rc which in turn runs the scripts in /etc/rc.d/rc#.d/. I don't see how this contradicts what I said?! Anders
On Fri, 28 Sep 2001, Anders Johansson wrote:
Just read /etc/rc.d/boot. Read the SOURCE and not comments to find out facts.
I have. /etc/rc.d/boot is run by init as the first thing by init. This is followed by running /etc/rc.d/rc which in turn runs the scripts in /etc/rc.d/rc#.d/. I don't see how this contradicts what I said?!
Ok. Long explanation. First, I haven't actually tried it... I only looked at the sources (shell). - Start with /etc/inittab There's no 'sysinit' and no 'boot', only a 'bootwait' (these three entries are possible for what will be the very first process init calls) The bootwait line starts /etc/init.d/boot - Let's go to /etc/init.d/boot Wait a moment... I take back everything I said, it is as you said. It's time I read the SuSE README in /etc/init.d/ about the SuSE boot concept... But it shows again: That's what I like about working in the US rather than in Germany. In Germany, you do everything right and are polite, and the customers (at least an incredibly high number, of course not all) will tell you how disappointed they are with your service and your high prices. This is not just an opensource thing, about a year ago in the editorial section of one of the best Computer papers in the world (iX, nothing like it in the US, here every magazine is 70% ad's and the rest isn't that good either; unfortunately they are not ambitious enough to try to conquer the US market, like many German companies) the author wrote about his personal experiences with feedback mail to them. The one thing I remember was a student who asked him lots of questions that clearly needed lots of research which the student could do himself, all for a scientific paper that guy had to write, and he complained bitterly when the iX-writer very politely pointed this out about the "utter lack of service". Strange enough, the Germans always look to America when they talk about how the "service culture" is under-developed in Germany. If only they knew (they never tried to get a "service representative" to do something that's not directly in his reference book - I recently tried to open a bank account and "only" have a cellphone, and the company pays and not me, but their procedures require address verification via the phone numver...)! People here are content with so little. This was another good example. I write complete BS and the one who apologizes is... the other person (obviously American). I love this country, it's great to do business in ;-) Michael
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.
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
On Friday 28 September 2001 15:09 pm, 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.
I made up my own. Added an S99local to /etc/init.d/rcx.d where x = 2,3,4,5 and made it a sym link to /etc/init.d/rc.local Works just fine. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/28/01 15:20 + +----------------------------------------------------------------------------+ 'I shop, therefore I am.' Tammy Bakker and Imelda Marcos
On Fri, 28 Sep 2001 11:09:04 -0700
Michael Hasenstein
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.
And you would be in error for not reading my original post. I had called bot.local rc.boot by mistake, but had stated that it gets called before the init scripts, so was no good. Can't really make a network call if the network is not up, hum?
participants (5)
-
Anders Johansson -
Bruce Marshall -
Michael Hasenstein -
Timothy Reaves -
Tom Wesley