🚀 go-pugleaf

* Christopher R Barry wrote:

> I did a lot of Find String commands to replace every last occurance of
> the old IPs with the new yet whenever I tried to use host TRILOGY like
> e.g. Edit File TRILOGY:>cbarry>whatever I would get a window about
> "Host Trilogy (192.42.172.3)" being unreachable. The old IP was
> somehow persisting despite my attempts to replace every last trace of
> it. So in order to access files I would have to do
> INTERNET|192.168.0.2:>....

That's a bad way of doing things to the namespace files because they
are file-version sensitive -- you *can* do it, but you have to either
fiddle with the file versions, or edit the thing that tells it which
version of what is the right one.

Assuming your setup is fairly simple, I think it's better to use the
namespace editor  -- boot the machine with the old-but coherent IP
address, then edit (with edit namespace object) the places where it
knows about the address, which will be at least the network object,
the machine, and the objects for any other machines it knows.

If you then do a reset network, I think it *should* start using the
new IP address.  If it doesn't then editing the boot file and
rebooting should work.

This may not be accurate, but it definitely is possible to do it like
this, as I did it with an nxp, which is even worse because at various
crucial points the X display which is pretty much the only connection
you have to the machine goes away as the IP address changes...

--tim