On Wed, 2003-12-31 at 01:46, John Andersen wrote:
Have the same problem with my Pcmcia card Chuck.
man insserv
Insserv sets the order of those links based on the requirements that are in the individual files. Theoretically, you should be able to edit the /etc/init.d/pcmcia and add network as one of the "requires" options, and insserv should calculate the order.
But when you do this you get a nasty loop condition and insserv refuses to set anything.
Yep happened to me as well. No matter how I edited the files PCMCIA always gets set to S08pcmcia. At one point the startup order was significantly different from what it was before I started to the point I was afraid to restart the computer out of fear that it would not start up properly. I had made back copies of each the init scripts before I edited them so if things got out of hand I could restore them. Evidently, there is some other file that I am not aware of that is part of this process as even after I restored them and ran insserv -d the order did not return to the way it was before I started. Fortunately, I had captured the start order to a text file so I could manually rename to files as a last resort. I have spent the last two days reading documentation on insserv. While I understand the concepts, it is just not complete enough for someone other than the programmers who wrote it to understand how to configure the init scripts to get services to start in a particular order.
I havent found the solution yet, but thats the direction I'm looking at the present time.
If you get it figured out I would appreciate you letting me know. I've got a spare laptop that I'm going to install Suse on and play around with the scripts to see if I figure it out. I'll keep the list posted.
On Thu, 2004-01-01 at 16:09, Chuck Stuettgen wrote:
On Wed, 2003-12-31 at 01:46, John Andersen wrote:
Have the same problem with my Pcmcia card Chuck.
man insserv
Insserv sets the order of those links based on the requirements that are in the individual files. Theoretically, you should be able to edit the /etc/init.d/pcmcia and add network as one of the "requires" options, and insserv should calculate the order.
But when you do this you get a nasty loop condition and insserv refuses to set anything.
Yep happened to me as well.
No matter how I edited the files PCMCIA always gets set to S08pcmcia.
At one point the startup order was significantly different from what it was before I started to the point I was afraid to restart the computer out of fear that it would not start up properly. I had made back copies of each the init scripts before I edited them so if things got out of hand I could restore them. Evidently, there is some other file that I am not aware of that is part of this process as even after I restored them and ran insserv -d the order did not return to the way it was before I started.
Fortunately, I had captured the start order to a text file so I could manually rename to files as a last resort.
I have spent the last two days reading documentation on insserv. While I understand the concepts, it is just not complete enough for someone other than the programmers who wrote it to understand how to configure the init scripts to get services to start in a particular order.
I havent found the solution yet, but thats the direction I'm looking at the present time.
If you get it figured out I would appreciate you letting me know.
I've got a spare laptop that I'm going to install Suse on and play around with the scripts to see if I figure it out.
I'll keep the list posted.
Well now I'm really stumped. I installed SuSE 9 Pro on a second Dell laptop (Inspiron 4000). Then manually renamed S08pcmcia in /etc/rc.d/rc5.d to S04pcmcia so PCMCIA would start before the network. I rebooted the laptop to make sure everything worked which it did. Then I ran YOU and installed all the updates. Suseconfig did it's thing and guess what? It left S04pcmcia alone. I then spent the next two hours in Yast reconfiguring the built in Ethernet adapter and the Linksys WPC11 wireless adapter in various ways including deleting them both and recreating them. Each time letting suseconfig do its thing. Not once did Suseconfig change S04pcmcia to something else. So if anyone has any more suggestions I would like to hear them. In the mean time I think I'm going to send a message to Werner Fink at Suse the author of insserv and see what his thoughts are. -- Chuck Stuettgen <cstuettgen@myrealbox.com> http://www.cfs-tech.homelinux.net
On Thursday 01 January 2004 18:41, Chuck Stuettgen wrote:
So if anyone has any more suggestions I would like to hear them. In the mean time I think I'm going to send a message to Werner Fink at Suse the author of insserv and see what his thoughts are.
Run insserv -d and see what it does to your configuration. I think you will find it gets set back. Somewhere in the process this will get run and when you least expect it your system reverts to that which the scripts define by thier "required start" and "provides" lines. insserv.conf (i think thats the name) gets involved too. There is definitly some bit missing from the docs. I'd be interested in what Werner says. I note that Mantel had a hand in some of these things as well. -- _____________________________________ John Andersen
On Fri, 2004-01-02 at 04:41, John Andersen wrote:
On Thursday 01 January 2004 18:41, Chuck Stuettgen wrote:
So if anyone has any more suggestions I would like to hear them. In the mean time I think I'm going to send a message to Werner Fink at Suse the author of insserv and see what his thoughts are.
Run insserv -d and see what it does to your configuration. I think you will find it gets set back. Somewhere in the process this will get run and when you least expect it your system reverts to that which the scripts define by thier "required start" and "provides" lines.
insserv.conf (i think thats the name) gets involved too. There is definitly some bit missing from the docs. I'd be interested in what Werner says. I note that Mantel had a hand in some of these things as well.
You are correct. I ran insserv -d and it changed PCMCIA back to start after the network. -- Chuck Stuettgen <cstuettgen@myrealbox.com> http://www.cfs-tech.homelinux.net
participants (2)
-
Chuck Stuettgen -
John Andersen