Re: [SLE] SuSeconfig Question - Update
John Andersen
On Thursday 01 January 2004 18:41, Chuck Stuettgen wrote:
So if anyone has any more suggestions I would like to hear them. =A0In 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.
The problem is caused by the syslog dependency -- if you either remove $network from syslog, or $syslog from pcmcia then insserv -d will obey the network's 'Required-Start: $pcmcia' line. (If you do remove $network from syslog you will probably have to replace it with $local_fs however.)
On Fri, 2004-01-02 at 04:50, Mark Gray wrote:
John Andersen
writes: On Thursday 01 January 2004 18:41, Chuck Stuettgen wrote:
So if anyone has any more suggestions I would like to hear them. =A0In 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.
The problem is caused by the syslog dependency -- if you either remove $network from syslog, or $syslog from pcmcia then insserv -d will obey the network's 'Required-Start: $pcmcia' line.
(If you do remove $network from syslog you will probably have to replace it with $local_fs however.)
That was the trick.
Having said this - you should be aware that it appears there is a
dependency between when you run insserv -d and the order of the entries
in the init files.
On my test laptop, (Inspiron 4000), I removed both network entries from
syslog and added $local_fs to the Required-Start: line. I left the
Required-Stop: line blank.
Then I removed both network and hotplug entries from PCMCIA. When I ran
insserv I got the following start order.
S01pcmcia
S01random
S01syslog
S03resmgr
S05network
S06hotplug
S08portmap
S08smbfs
S08splash_early
S12acpid
S12alsasound
S12fbset
S12sshd
S13cpufreqd
S13cups
S13kbd
S13splash
S14cron
S14hwscan
S14nscd
S15splash_late
S15xdm
As you can see I PCMCIA starts first. When I duplicated the same edits
on my Latitude laptop I got several warnings and a different order. I
added the hotplug entry back in the PCMCIA script then ran insserv I
still got warnings. I then added the network entry back to PCMCIA but
put it after hotplug and ran insserv again. This time I did not get any
errors or warnings and PCMCIA the first service to start.
So to recap this is what I had to do to get PCMCIA to start first on my
Latitude laptop.
I removed both network entries from syslog and added $local_fs to the
Required-Start: line. I left the Required-Stop: line blank.
I also changed the order of the X-UnitedLinux-Should-Start: line in
pcmcia. I reversed the of network and hotplug to hotplug network.
When I ran insserv -d it results in the following start order in rc5.d:
S01pcmcia
S01random
S01syslog
S02hotplug
S03resmgr
S05network
S05portmap
S05splash_early
S06smbfs
S09acpid
S09alsasound
S09fbset
S09sshd
S10cpufreqd
S10cups
S10kbd
S10splash
S11hwscan
S11smpppd
S12xdm
S13cron
S13nscd
S14splash_late
* * *
To summarize you just have to experiment. But make one change at a time
and run insserv between each change.
Thanks to every one who posted and especially John Anderson and Mark
Gray.
Now all we have to worry about is SuSE updating the init scripts. :-)
--
Chuck Stuettgen
The Friday 2004-01-02 at 14:26 -0600, Chuck Stuettgen wrote:
* * *
To summarize you just have to experiment. But make one change at a time and run insserv between each change.
Theoretically, the pcmcia script should start its network part automatically. That should be /etc/hotplug/net.*
Now all we have to worry about is SuSE updating the init scripts. :-)
I think it must be designed to work diferently that what you are thinking about :-) -- Cheers, Carlos Robinson
On Sat, 2004-01-03 at 20:46, Carlos E. R. wrote:
The Friday 2004-01-02 at 14:26 -0600, Chuck Stuettgen wrote:
* * *
To summarize you just have to experiment. But make one change at a time and run insserv between each change.
Theoretically, the pcmcia script should start its network part automatically.
That should be /etc/hotplug/net.*
In theory. In practice however, hotplug fails miserably. I have installed both 8.2 and 9.0 on two laptops and one of my co-workers has installed both versions on his laptop and in all cases PCMCIA fails to get a network connection on boot. Hotplug seems to work for USB devices but thats all.
Now all we have to worry about is SuSE updating the init scripts. :-)
I think it must be designed to work diferently that what you are thinking about :-)
I don't understand your point?
--
Chuck Stuettgen
The Saturday 2004-01-03 at 23:13 -0600, Chuck Stuettgen wrote:
Theoretically, the pcmcia script should start its network part automatically.
That should be /etc/hotplug/net.*
In theory. In practice however, hotplug fails miserably. I have installed both 8.2 and 9.0 on two laptops and one of my co-workers has installed both versions on his laptop and in all cases PCMCIA fails to get a network connection on boot.
Hotplug seems to work for USB devices but thats all.
Mmm. Unfortunately, I don't have a portable at the moment, so I can't test it. On SuSE 7.3 I got it working, two years ago.
Now all we have to worry about is SuSE updating the init scripts. :-)
I think it must be designed to work diferently that what you are thinking about :-)
I don't understand your point?
That SuSE must have designed it's scripts to work, and portables with network on pcmcia is a typical situation, so it has got to work, somehow. We must be looking at it the wrong way. -- Cheers, Carlos Robinson
On Sun, 2004-01-04 at 18:47, Carlos E. R. wrote:
The Saturday 2004-01-03 at 23:13 -0600, Chuck Stuettgen wrote:
Theoretically, the pcmcia script should start its network part automatically.
That should be /etc/hotplug/net.*
In theory. In practice however, hotplug fails miserably. I have installed both 8.2 and 9.0 on two laptops and one of my co-workers has installed both versions on his laptop and in all cases PCMCIA fails to get a network connection on boot.
Hotplug seems to work for USB devices but thats all.
Mmm. Unfortunately, I don't have a portable at the moment, so I can't test it. On SuSE 7.3 I got it working, two years ago.
Now all we have to worry about is SuSE updating the init scripts. :-)
I think it must be designed to work diferently that what you are thinking about :-)
I don't understand your point?
That SuSE must have designed it's scripts to work, and portables with network on pcmcia is a typical situation, so it has got to work, somehow. We must be looking at it the wrong way.
I would agree it should work.
Hotplug is not the only thing that doesn't work right. There is also a
problem with the stability of wireless networking in SuSE.
I don't know exactly where the problem lies yet but it seems to be with
the DHCP client and how it sets the default route or the DNS entries.
I have been losing the default route and the DNS information at random
intervals. I have had to constantly restart the network. Sometimes I
would have to restart it four or five time in an hour.
In order to try and track the problem, two days ago I statically set all
of the network information for the wireless card instead of getting it
from the DHCP server in my router. Since then I have not lost the route
- DNS - network connection one time.
<soapbox>
Until I loaded SuSE two months ago, I had been running Mandrake Linux,
(7.2, 8.0, 8.2, 9.0), with the same wireless network hardware I'm using
now, on my laptops for three years. In all that time I *never* had a
problem with losing my network connection.
The fact that Novell announced their intention to purchase SuSE is what
prompted me to try SuSE Linux. Novell has long had a reputation for
building solid products. It is my hope that with Novell's support, the
SuSE developers will be able to build a SOLID Linux distribution that
will make all other Linux distributions seem like beta software
including my favorite Mandrake.
</soapbox>
--
Chuck Stuettgen
The Sunday 2004-01-04 at 22:48 -0600, Chuck Stuettgen wrote:
I don't understand your point?
That SuSE must have designed it's scripts to work, and portables with network on pcmcia is a typical situation, so it has got to work, somehow. We must be looking at it the wrong way.
I would agree it should work.
Hotplug is not the only thing that doesn't work right. There is also a problem with the stability of wireless networking in SuSE.
I can't even try to duplicate your situation.
I don't know exactly where the problem lies yet but it seems to be with the DHCP client and how it sets the default route or the DNS entries.
There are also some entries on the SDB that might apply to your case.
I have been losing the default route and the DNS information at random intervals. I have had to constantly restart the network. Sometimes I would have to restart it four or five time in an hour.
In order to try and track the problem, two days ago I statically set all of the network information for the wireless card instead of getting it from the DHCP server in my router. Since then I have not lost the route - DNS - network connection one time.
Then perhaps there is a problem with the dhcp client - there are two you can choose from. I excerpt some text from the SuSE admin book: DHCP Software Packages Both a DHCP server and DHCP clients are available for SuSE Linux. The DHCP server available is dhcpd (published by the Internet Software Consortium). On the client side, you can choose between two different DHCP client programs: package dhclient (also from ISC) and the ``DHCP client daemon'' in the package dhcpcd package. SuSE Linux installs dhcpcd by default. The program is very easy to handle and will be launched automatically on each system boot to watch for a DHCP server. It does not need a configuration file to do its job and should work out of the box in most standard setups. For more complex situations, use the ISC dhclient, which is controlled by means of the configuration file /etc/dhclient.conf. Maybe the "other one" works for you. -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R.
-
Chuck Stuettgen
-
Mark Gray