man insserv
Also look at the header comment in /etc/rc.d/skeleton. The comments
between "INIT INFO" is used to give the order dependencies and is used
to set the order of initialization when booting, or changing run
levels (e.g., halting, rebooting).
HTH,
Jeffrey
Quoting Gnu iBook 2
Sorry if I am too confused here. SuSE has changed the location of these files over the last few versions, no? So I have /etc/init.d/pcmcia
Now I need to modify this file, right? There is no mention of insserv anywhere in the file. can you clarify exactly what I should be typing into this file?
On Wednesday, December 19, 2001, at 02:16 PM, Jeffrey Taylor wrote:
Okay, /etc/rc.d/pcmcia
Quoting Gnu iBook 2
: I don't have a /etc/rc.d/init.d/ directory.
On Wednesday, December 19, 2001, at 01:41 PM, Jeffrey Taylor wrote:
Add a header for insserv to /etc/rc.d/init.d/pcmcia or correct the one that's there.
Jeffrey
Quoting Gnu iBook 2
: I have a SuSE 7.3 system running on a Compaq LTE 5000 laptop which I have setup as a Wireless LAN Access Point. I had to rebuild the pcmcia package with the drivers for my wlan card, but it is working ok right now. I have also installed and configured the SuSEfirewall2 package, which seems to be working, more or less.
There is a little problem with this configuration though. On boot-up, I get an error message from the firewall saying that the wlan interface is not running. I found that is because, in rc3.d, the firewall starts at S08, but pcmcia not until S09. So I renamed S09pcmcia to S05pcmcia, the same S# as network. That fixed it, I no longer got the error message.
However, then I went and changed the configuration of the pcmcia card through yast. And then pcmcia went back to S09, and I have the startup error again. How can I tell yast not to change this? Or better yet, tell it that S05 is correct.
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck