Message-ID: <39CA4AEE.B00C64E6@pacbell.net> From: Scott Neugroschl <firstname.lastname@example.org> Newsgroups: comp.unix.sco.misc Subject: Re: Why does the network manager relink for IP changes X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly Date: Thu, 21 Sep 2000 10:52:46 -0700 It's because of the "kernel slink" module (ksl). For efficiency reasons, SCO put the slink module (which builds the TCP/IP STREAMS stack) into the kernel. This can be disabled using ksl.disable in the bootstring. Of course, if you want, you can use ifconfig to change addresses, it just won't be permanent. Personally, I thought this was a stupid decision, myself. Tony Lawrence wrote: > > Andrew Habgood wrote: > > > > If I change the IP address of my NIC with the Network Manager, it requires a > > relink. However I can use ifconfig without one. Does the Network Manager > > do anything differently? Besides leaving the old ip in /etc/hosts ;-) > > One reason for the relink (and it may be the only reason, I > dunno) is so that the low-level kernel routines know the > machines IP address- if you've ever pinged an OSR5 or UW > server while they were in single user mode, you will have > noticed that it responds- without tcp/ip running, and to do > that it would need to know its address. > > -- > Tony Lawrence (email@example.com) > SCO/Linux articles, help, book reviews, tests, > job listings and more :
Got something to add? Send me email.