Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site t4test.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!decwrl!sun!idi!t4test!chip From: chip@t4test.UUCP (Chip Rosenthal) Newsgroups: net.bugs.uucp Subject: Re: How to change nodenames Message-ID: <1126@t4test.UUCP> Date: Mon, 17-Sep-84 05:40:51 EDT Article-I.D.: t4test.1126 Posted: Mon Sep 17 05:40:51 1984 Date-Received: Tue, 25-Sep-84 04:42:25 EDT References: <750@enea.UUCP> Organization: Intel, Santa Clara, Ca. Lines: 32 Summary: and a big foo on `uuxqt' --- REFERENCED ARTICLE --------------------------------------------- >Subject: How to change nodenames >Newsgroups: net.bugs.uucp >From: ber@enea.UUCP (Bjorn Eriksen) >Date: Mon, 10-Sep-84 19:51:49 PDT > >Vendors shouldn't send out systems with default names if there isnt't >any way to change it locally. Does anyone know how nodenames are >changed in different brands of Unix? -------------------------------------------------------------------- What I find a real bummer (along the lines of Bjorn's complaint) is that what `uuxqt' can do is compiled right into the program. What a wonderful deal for sites without a source license, like us. [ :-) for extreme sarcasm ] Our problem is that we are trying to use uucp to keep the file systems of two VAXEN identical. One of the guys here developed some programs to do it. Guess what he called the one executed by uuxqt. It is called "w". (Heh. Heh. Imagine the surprise when somebody tries to do a remote "w" on one of our systems.) Does anybody have any better ways of getting around this problem? *sigh* What can you say about an operating system where half of the documentation is in the source code. -- Chip Rosenthal, Intel/Santa Clara { idi|intelca|icalqa|kremvax|qubix|ucscc } ! t4test ! { chip|news }