Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!caen!umich!terminator!dabo.citi.umich.edu!rees
From: rees@dabo.citi.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: mysterious hint file on HP/Domain/OS
Keywords: hint
Message-ID: <50da0037.cb12@dabo.citi.umich.edu>
Date: 8 Apr 91 14:50:03 GMT
References: <885@imec.UUCP> <50cad431.cb12@dabo.citi.umich.edu> <2679@prles2.prl.philips.nl>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan ITD
Lines: 19

In article <2679@prles2.prl.philips.nl>, hooft@prl.philips.nl (Peter van Hooft) writes:

  |In general, you need to remove all hint files and reboot all nodes whenever
  |a node moves from one network to another, or net numbers change.
  
  No. When you move a machine to another net, you only have to ctnode -root 
  it, or "replace" the entry in the naming server database (using edns) with 
  the new netid instead of the old one.

I hate to contradict you, but as of sr9.7 you certainly had to remove and
reboot all nodes if any changed net ids.  I know this because I did some
work on the hint file code myself at that time.  I don't think this has
changed since then, but I could be wrong.  I haven't tried it.

  If I _had to_ change net numbers, I would do it like this:
  [ complicated 6 step procedure deleted ]

I always use my IP address as my Domain net address.  This worked fine until
the University helpfully decided to change all our IP addresses.