Path: utzoo!attcan!uunet!cs.utexas.edu!rice!sun-spots-request
From: richard@chook.ua.oz.au (Richard Siggs)
Newsgroups: comp.sys.sun
Subject: Re: Changing Client IP Address
Keywords: Networks
Message-ID: <9515@brazos.Rice.edu>
Date: 2 Jul 90 05:00:50 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 24
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n205, Replies: v9n205
X-Sun-Spots-Digest: Volume 9, Issue 235, message 13

In article <8715@brazos.Rice.edu>, woodb!tkevans@cs.umd.edu writes:
[stuff deleted]
|>
|>Now, however, we have a shiny new domain name and Class B IP address.  As
|>a result, I need to change all the IP addresses we have been using.
|>
|>From TFM, it appears the client looks for a file /tftpboot named with the
|>hex equivalent of its IP address, a file which is symbolically linked to
|>/tftpboot/boot.sun3.  Could I just rename this file to the hex equivalent
|>of its new IP address?  Will the client boot?  If so, are there any other
|>fixes needed to properly implement this workaround?  Thanks.

As far as I know (I've done it many times), you can just rename the file
in tftpboot to the new IP address in hex, however, be careful about
permissions on files in /tftpboot, as tftp is pretty dumb. I've also found
that the client needs its server's IP number in its /etc/hosts file (even
if it's YP served, as YP comes up after such things as mounting root
disks...)

Richard Siggs			| "As the joys of Heaven are enjoyed by men,
Computer Science Dept.,		|  so shall the pains of Hell be suffered.
Adelaide University,		|  For they will be men still,
South Australia.		|  so they will act and feel as men."
ACSnet: richard@cs.ua.oz.au	|	- quote from the film "Bliss".