Changing server IP address
dro...@my-deja.com
change the machine's IP address?
Our corporate office has asked (demanded) we change our internal IP
scheme ASAP so they can install a router. Unfortunately, our kernel
will not recompile (dies with
a /var/opt/K/SCO/link/1.1.1Ga/etc/conf/pack.d/ks1/space.c line 438
error) and we have been unable to proceed.
Alternatively, does anyone know any SCO consultants in the Dallas/Fort
Worth area? Our current consultant thinks we probably need to
completely re-install SCO but is opting out of doing it.
Thanks for your help.
Sent via Deja.com
http://www.deja.com/
bcr...@attglobal.net
> Is it necessary to recompile the kernel under SCO Openserver 5 to
> change the machine's IP address?
Yes.
>
>
> Our corporate office has asked (demanded) we change our internal IP
> scheme ASAP so they can install a router. Unfortunately, our kernel
> will not recompile (dies with
> a /var/opt/K/SCO/link/1.1.1Ga/etc/conf/pack.d/ks1/space.c line 438
> error) and we have been unable to proceed.
>
Check the sco.com for a TA that addresses this.
>
> Alternatively, does anyone know any SCO consultants in the Dallas/Fort
> Worth area? Our current consultant thinks we probably need to
> completely re-install SCO but is opting out of doing it.
>
You do not need to reinstall. You need to read (Thanks to Jeff
Liebermann): http://www.cruzio.com/~jeffl/sco/new_name.txt
To look for consultants, check out www.pcunix.com for an informal list of
consultants.
>
> Thanks for your help.
>
> Sent via Deja.com
> http://www.deja.com/
Ben Rosenthal
bcrosen
@
attglobal.net
John Gray
Nope, go single user mode and edit /etc/tcpip. look for the ifconfig
line.
then type init 2 to go multi user.
-john
Bill Vermillion
Usually single errors like that aren't that hard to correct. I
only had to re-install one SCO system where I'd got errors like
that. It turns out there were several files corrupt deep in the
/var/opt/an/impossibly/long/path/directory areas. So many I gave up
as I was starting to feel like Sysyphus, but it was not a rock
I was rolling but something left by a dung beatle.
But depending on the router they are planning on installing, you
can perhaps set it up for NAT and PAP. You essentially map your
wrong IP address to one of the non-routable groups, eg the 192.168,
10, or 17.16, and remap those on the incoming side to the new IP
addresses. This is sometimes used in lieu of changing IP's on
hundreds or thousands of machines.
--
Bill Vermillion - bv @ wjv . com
David Mabo
when I track down the script that creates ksl, I found, removed it and
recompiled. ksl is created by kslgen, and that is where you need to do
your research.
--
David H. Mabo, CPCM
Adaptix Corp. - Cincinnati, Ohio
Cray Drygu
>dro...@my-deja.com wrote:
>
>> Is it necessary to recompile the kernel under SCO Openserver 5 to
>> change the machine's IP address?
>
>Yes.
Slightly off-topic for this thread, but can anyone explain to me *why*
OSR5 needs a kernel recompile to change the IP address? I thought it
was bad enough that Windows requires a reboot, when I found out systems
like Linux, BSD, BeOS etc can change it on-the-fly. But a kernel
recompile?
--
cray [at] org
silverlight [dot]
Bill Vermillion
>>Yes.
The core designs of Linux, BSD, Beos are all much newer than the
Sys V.3 base of OSR5. The first V.3 release from AT&T was about
1989 and I got my first in early 1990.
Steve Fabac
>
> bcr...@attglobal.net wrote in <3A6E0752...@attglobal.net>:
>
> >dro...@my-deja.com wrote:
> >
> >> Is it necessary to recompile the kernel under SCO Openserver 5 to
> >> change the machine's IP address?
> >
> >Yes.
In my experience, no.
Try it your self: Run netconfig and change the IP address on the NIC.
Defer rebuilding the kernel on exit from netconfig.
Change to /etc/conf/cf.d and type ./link_unix and answer N to "boot
by default."
Execute cmp -l unix /unix and note that only three or four bytes of the
kernel at about the fifth byte from the beginning have been changed.
If you re-link and install the kernel before you run netconfig, then
run netconfig, change the IP and exit netconfig, then re-link (but don't
install the kernel) cmp -l will show that nothing in the kernel has
been changed by running netconfig and re-linking.
> Do you want this kernel to boot by default? (y/n) n
>
> The new kernel is in the directory /etc/conf/cf.d, to make
> this kernel bootable copy it onto the boot file system.
>
> Device node or inittab changes associated with this new kernel
> have not been made. These changes should be made by running
> touch /etc/.new_unix; /etc/conf/bin/idmkenv.
> # cmp -l unix /unix
> 5 56 350
> 6 240 277
> 7 157 365
> 8 72 71
> #
Netconfig at minimum changes the settings in /etc/tcp. Anything else is
unknown.
so in the case of the original poster: Run netconfig to change the IP
address. Answer no to relink the kernel. Shutdown and reboot.
"/etc/tcp stop" followed by "/etc/tcp start" may work but don't count
on it.
Steve Fabac
S.M. Fabac & Associates
816/765-1670
Tom Parsons
| Cray Drygu wrote:
| >
| > bcr...@attglobal.net wrote in <3A6E0752...@attglobal.net>:
| >
| > >dro...@my-deja.com wrote:
| > >
| > >> Is it necessary to recompile the kernel under SCO Openserver 5 to
| > >> change the machine's IP address?
| > >
| > >Yes.
|
| In my experience, no.
Weren't you having ksl_gen problems a few months ago? A good way
to provoke them is to skip kernel relinks.
| Try it your self: Run netconfig and change the IP address on the NIC.
| Defer rebuilding the kernel on exit from netconfig.
| Change to /etc/conf/cf.d and type ./link_unix and answer N to "boot
| by default."
| Execute cmp -l unix /unix and note that only three or four bytes of the
| kernel at about the fifth byte from the beginning have been changed.
|
| If you re-link and install the kernel before you run netconfig, then
| run netconfig, change the IP and exit netconfig, then re-link (but don't
| install the kernel) cmp -l will show that nothing in the kernel has
| been changed by running netconfig and re-linking.
You are assuming that nothing else is rebuilt on a reboot. Bad assumption,
it is like to bite you.
Rebooting isn't that big an issue and it ensures that all caches are
flushed (like arp) and dynamic tables are rebuilt.
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
Steve Fabac
> Steve Fabac enscribed:
> | Cray Drygu wrote:
> | >
> | > bcr...@attglobal.net wrote in <3A6E0752...@attglobal.net>:
> | >
> | > >dro...@my-deja.com wrote:
> | > >
> | > >> Is it necessary to recompile the kernel under SCO Openserver 5 to
> | > >> change the machine's IP address?
> | > >
> | > >Yes.
> |
> | In my experience, no.
>
> to provoke them is to skip kernel relinks.
Yep,
The system was an upgrade from 5.0.2 to 5.0.5 on a DEC Pentium box.
Fresh install on a new hard drive in another box, then moved to the DEC.
This was when 5.0.5 was first available and we experienced many problems
with systems combining Digi Xem host adapters and 3COM 3c905b NIC's.
During the installation and debugging we loaded new drivers for the
3C985 and then removed the 905 with netconfig and custom to remove the
added drivers. We then installed the latest (at the time) drivers for
the Intel Pro100.
Something became corrupted and ksl_gen insisted on including a phantom
3C905 as net0 and the Pro100 was net1. It took awhile to ferret out the
problem and patch the configuration files so that the Pro100 was net0
and the phantom 3C905 was gone.
The system is running happily today with the Intell Pro100 NIC.
>
> | Try it your self: Run netconfig and change the IP address on the NIC.
> | Defer rebuilding the kernel on exit from netconfig.
> | Change to /etc/conf/cf.d and type ./link_unix and answer N to "boot
> | by default."
> | Execute cmp -l unix /unix and note that only three or four bytes of the
> | kernel at about the fifth byte from the beginning have been changed.
> |
> | If you re-link and install the kernel before you run netconfig, then
> | run netconfig, change the IP and exit netconfig, then re-link (but don't
> | install the kernel) cmp -l will show that nothing in the kernel has
> | been changed by running netconfig and re-linking.
>
> You are assuming that nothing else is rebuilt on a reboot. Bad assumption,
> it is like to bite you.
>
> Rebooting isn't that big an issue and it ensures that all caches are
> flushed (like arp) and dynamic tables are rebuilt.
Tom, the following is part of my post that you omitted from your reply.
I have added it back in so that all my read and judge my statement:
> | Netconfig at minimum changes the settings in /etc/tcp. Anything else is
> | unknown.
> |
> | so in the case of the original poster: Run netconfig to change the IP
> | address. Answer no to relink the kernel. Shutdown and reboot.
> |
> | "/etc/tcp stop" followed by "/etc/tcp start" may work but don't count
> | on it.
Note that I indicated that a reboot after Netconfig was advisable. Also,
the original poster had indicated that he was unable to rebuild the
kernel after using netconfig to change the IP of the system.
My point is that he can successfully change the IP with Netconfig, skip
the kernel rebuild and then re-boot to effect the change in IP address.
This is not a recommendation for a standard operating procedure.
Admittedly, if the original poster is unable to rebuild the kernel, he
has a crippled system that will have to be repaired or replaced
(reinstalled) at some point in the future.
I miss 3.2v4.2 where you could pull a clean link kit from the
distribution media using custom, and then re-install your drivers to
fix a buggered link kit. I tried that once with 5.0.2 and it did not
work. That system had to be reinstalled to fix the problem.
Steve Fabac
S.M. Fabac & Associates
816/765-1670
Tom Parsons
| Tom Parsons wrote:
| > Steve Fabac enscribed:
| > | Cray Drygu wrote:
| > | >
| > | > bcr...@attglobal.net wrote in <3A6E0752...@attglobal.net>:
| > | >
| > | > >dro...@my-deja.com wrote:
| > | > >
| > | > >> Is it necessary to recompile the kernel under SCO Openserver 5 to
| > | > >> change the machine's IP address?
| >
| > Weren't you having ksl_gen problems a few months ago? A good way
| > to provoke them is to skip kernel relinks.
|
| Yep,
|
| The system was an upgrade from 5.0.2 to 5.0.5 on a DEC Pentium box.
| Fresh install on a new hard drive in another box, then moved to the DEC.
|
| This was when 5.0.5 was first available and we experienced many problems
| with systems combining Digi Xem host adapters and 3COM 3c905b NIC's.
|
| During the installation and debugging we loaded new drivers for the
| 3C985 and then removed the 905 with netconfig and custom to remove the
| added drivers. We then installed the latest (at the time) drivers for
| the Intel Pro100.
Yep, I tried that once, skipped the kernel reboot and viola, same problem
you had. Dig into the internals and you will find the kslgen routines
dynamically built some areas on reboot.
Bill Vermillion
>I miss 3.2v4.2 where you could pull a clean link kit from the
>distribution media using custom, and then re-install your drivers to
>fix a buggered link kit. I tried that once with 5.0.2 and it did not
>work. That system had to be reinstalled to fix the problem.
Thank goodness for that feature in 3.2v4.2. I had some vendor
supplied drivers that would fail an install, and in the process of
cleaning up after themselves, would remove more than what they were
supposed to.
I think I reloaded the link kit at least 4 times that day.
The vendor finally sent me some information where I had to
manually change the settings in their files in the /etc/conf
arena, as the shell install scripts would torch things if you did
not use the typical no brainer, accept all defaults install.
3.2v4.2 was really pretty good.