Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ptsfb.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!intelca!qantel!ptsfa!ptsfb!jon
From: jon@ptsfb.UUCP (Jon Gallagher)
Newsgroups: net.unix-wizards,net.unix
Subject: Re: Callan UUCP system names on System-V, utsname.
Message-ID: <224@ptsfb.UUCP>
Date: Wed, 11-Sep-85 00:47:53 EDT
Article-I.D.: ptsfb.224
Posted: Wed Sep 11 00:47:53 1985
Date-Received: Wed, 18-Sep-85 03:53:18 EDT
References: <129@pyuxv.UUCP>
Reply-To: jon@ptsfb.UUCP (Jon Gallagher)
Organization: Pacific Bell, San Francisco
Lines: 41
Xref: watmath net.unix-wizards:14866 net.unix:5660

To: cim2@pyuxv.UUCP
Subject: Re: Callan UUCP system names on System-V, utsname.
Newsgroups: net.unix-wizards,net.unix
In-Reply-To: <129@pyuxv.UUCP>
Organization: Pacific Bell, San Francisco
Cc: 
Bcc: 

	It's been our experience that the "setuname" coomand works
just fine on System V and V.2. We distribute a system base on the CT
Megaframe and have /etc/rc do a setuname (based on files a `cat $file`
of two files, sysnam and nodename) on going to init 2. Subsequent
"uname" calls find the proper system name and nodename, just like the man
page says it should (:-} :-} :-} )We find this a lot easier 
than relinking /unix (which we ended up having to because there 
wasn't enough message queue space but...).
	Seriously, if you don't have to re-configure /unix
DON'T (you never what your supplier's gnomes have gotten into).
Use your (1M) utilities instead. 


Jon Gallagher
Pacific Bell

2600 Camino Ramon
San Ramon, CA 94583

(415) 823-2451

{ihnp4|dual}!ptsfa!pbcast!matt

-- 
Jon Gallagher
Pacific Bell

2600 Camino Ramon
San Ramon, CA 94583

(415) 823-2451

{ihnp4|dual}!ptsfa!pbcast!matt


Brought to you by Super Global Mega Corp .com