Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!mhuxm!mhuxf!mhuxi!mhuhk!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!rlgvax!dsi1!ron
From: ron@dsi1.UUCP
Newsgroups: net.bugs.uucp,net.micro
Subject: Re: help with uname()/uucp on Tandy 6000 - Vax 750 Link
Message-ID: <557@dsi1.UUCP>
Date: Fri, 28-Mar-86 22:52:39 EST
Article-I.D.: dsi1.557
Posted: Fri Mar 28 22:52:39 1986
Date-Received: Tue, 1-Apr-86 06:58:46 EST
References: <245@usfvax2.UUCP>
Reply-To: ron@dsi1.UUCP (Super User)
Organization: Dynamic Systems, Inc., Arlington VA
Lines: 56
Xref: watmath net.bugs.uucp:725 net.micro:14188

In article <245@usfvax2.UUCP> rsb@usfvax2.UUCP (Scot Boake) writes:
>
>I have been having some problems getting Usenet 2.10.1 running on a
>Tandy 6000 with Xenix 3.1.1.
>
You should probably abandon 2.10.1 and get yourself a copy of 2.10.2 or
even 2.10.3 Beta (If you can find it?)  There is code to do get the
system name from a file called "/usr/include/whoami.h", which if you
don't have you can easily create.  It's a one liner that reads as
follows:

#define sysname "your_site_name"

You could even modify this code to do an fgets on /etc/systemid which is
where Tandy, in their infinite wisdom (maybe Microsoft can take some of
the blame) chose to put the system or node name.  But creating whoami.h
is much easier.

>The first problem is that when uname() is called, it passes back a structure
>in which the member name 'nodename' is set to null instead of the system name.
>There is no documented way to fix this!  So I just wrote my own uname() and
>placed it in the archive libc.a.  Problem 1 Fixed.
>
The Above takes care of this obviously.

>Problem 2 is more fun... when I call my site which is going to feed us news,
>their uucp does not know who they are talking to.  (They are 'usfvax2' VAX 750
>running 4.2 BSD Unix) I hooked a terminal up in the modem line and saw the
>following.  "Shereusfvax2" sent from them.  My system sent "Shere" and no
>system name.  The LOGFILE on the usfvax2 said that they are talking to ""
>and proceeded to seed me ALL of the spooled up uucp files for all systems.
>
The UUCP that is supplied with the Tandy dev system is quite an atrosity
to begin with, but believe it or not, it really does work?  You need to
make sure that your system name is in /etc/systemid and also make sure
that you have an L.sys and USERFILE entry for 'usfvax2'.  You should not
worry about the fact that their UUCP sends Shere(sysname) while yours
only sends Shere, this is typical since many different flavors of UUCP
exist.  This will not cause any problems all that really need to be
there is the 'Shere' itself.  It sounds like one of two things is
happening to cause their system to not know who they are talking to; 1)
your sitename is not in /etc/systemid thus your UUCP is sending a NULL
sitename, or 2) Their UUCP is bashed and doesn't recognize you as a site
it knows.

>When the VAX calls the Tandy 6000 no problem.  Everything works fine.  But
>since it is a long distance call, we have to pick up the tab by polling them.
>
This make #1 above sound more accurate.  When they call you they know
who they are calling. When you call them they have no idea. Check your
/etc/systemid.  Make sure the file is globally readable.

--
Ron Flax  (ron@dsi1.UUCP)
ARPA:	dsi1!ron@seismo.arpa
UUCP:	..!{seismo, rlgvax, prometheus}!dsi1!ron