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 catnip.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!hjuxa!catnip!ben
From: ben@catnip.UUCP (Bennett Broder)
Newsgroups: net.bugs.uucp,net.micro
Subject: Re: help with uname()/uucp on Tandy 6000 - Vax 750 Link
Message-ID: <269@catnip.UUCP>
Date: Fri, 28-Mar-86 20:48:31 EST
Article-I.D.: catnip.269
Posted: Fri Mar 28 20:48:31 1986
Date-Received: Sat, 29-Mar-86 16:26:05 EST
References: <245@usfvax2.UUCP>
Organization: The Broder Residence, Holmdel, NJ  07733
Lines: 55
Xref: watmath net.bugs.uucp:724 net.micro:14164

In article <245@usfvax2.UUCP>, rsb@usfvax2.UUCP (Scot Boake) writes:
> [ Line Eater Do Your Thing ]
> 
> I have been having some problems getting Usenet 2.10.1 running on a
> Tandy 6000 with Xenix 3.1.1.

Since I recently brought up 2.10.3 on SCO Xenix System V, I may be of
some help.
 
> 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 only way to get uname to return the name of the system is to remake
the kernel.  If you have the development system, that shouldn't be a
problem.  Check through the files in your configuration directory, it is
pretty easy to find where node is defined.  (It is in /usr/sys/conf/master
on my system).  Then just type make, and copy then resulting kernel to
/xenix.
 
> 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.
> 
> 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.
> 
> At this time I am getting news from a AT&T 3b2/300 with no uucp problems but
> due to strange reasons, we need to start getting news directly from the vax.
> 
> I am assuming that uucp is using the uname() system call to get the nodename
> and since nodename is NULL, there is no system name being sent after the
> 'Shere'.  Since I DO NOT have the source I cannot prove / disprove this theory.

No, most versions of Xenix use a version of uucico derived from v7.
V7 uucico did not send Shere=sitename, but just Shere.

However, if your machine is sending any kind of Shere message when calling
the Vax, there is something seriously wrong with your uucp.  Shere
indicates that the machine is in slave mode, but the uucp node originating
the call should always be in *master* mode.  So if the "Shere" rather than
"Shere=sitename" was going to cause a problem, it should do it when the Vax
calls you.

Hope this was of some help.

-- 

Ben Broder
{ihnp4,decvax} !hjuxa!catnip!ben
{houxm,topaz}/