Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!vtserf!marchany
From: marchany@vtserf.cc.vt.edu (Randy Marchany)
Newsgroups: comp.unix.ultrix
Subject: Re: Ultrix 4.0 RIS looses
Message-ID: <1629@vtserf.cc.vt.edu>
Date: 18 Apr 91 13:57:23 GMT
References: <1991Apr17.212012.11522@jarvis.csri.toronto.edu>
Organization: Virginia Tech, Blacksburg, VA
Lines: 22

In article <1991Apr17.212012.11522@jarvis.csri.toronto.edu> cks@hawkwind.utcs.toronto.edu (Chris Siebenmann) writes:
> Loss 1: RIS insists you can only register machines in the same domain
>as your host. This is silly, since RIS can be used by anyone who can
>reach your machine via TCP/IP; getting around this requires installing
>bogus /etc/hosts names, installing the machines, and then fixing
>~ris/.rhosts.  And why does RIS insist on knowing the Ethernet
>addresses all the time?  I'm never going to try booting these machines
>via RIS, so I could care less; I made up bogus Ethernet addresses for
>them.
>
While RIS does insist that the machines are in the same domain, the easy
workaround is to enter an unqualified host name and then edit the
.rhosts file and add a line with the fully qualified host name. For
example, the host I want to add is foo.cs.vt.edu. I enter "foo" at the
RIS prompt, select the subsets etc. and exit RIS. I then edit .rhosts
and search for the line "foo root". I add a line "foo.cs.vt.edu root".
We have used RIS to download subsets to machines in different domains for a
number of years with no problems.
	-Randy Marchany		
	VA Tech Computing Center
	Blacksburg, VA 24060
INTERNET: marchany@vtserf.cc.vt.edu