🚀 go-pugleaf

[ 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.

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.

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.

I've talked to Tandy about this and their reply thus far has been tough
cookies.  (Gee Thanks! :-( )

Is anybody out there in net land using a Tandy 6000 to talk to a vax??

Scott Boake                                     Small Systems Consulting
(813) 544 - 8152 (Voice)                        4669 - 73rd Ave North Suite A
Nice Short Path :-)                             Pinellas Park, FL 33565
{akgub,gatech}!akgua!akguc!codas!peroa!ucf-cs!usfvax2!rsb