Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!JADE.BERKELEY.EDU!usenet
From: usenet@JADE.BERKELEY.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Submission for mod-computers-vax
Message-ID: <8703150724.AA17507@jade.berkeley.edu>
Date: Sun, 15-Mar-87 02:24:08 EST
Article-I.D.: jade.8703150724.AA17507
Posted: Sun Mar 15 02:24:08 1987
Date-Received: Sun, 15-Mar-87 23:43:12 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 53
Approved: info-vax@sri-kl.arpa

Path: jade!violet.berkeley.edu!jkh
From: jkh@violet.berkeley.edu (Jordan K. Hubbard)
Newsgroups: mod.computers.vax
Subject: Weird problem with Vaxstation 2000 serial port
Message-ID: <2808@jade.BERKELEY.EDU>
Date: 15 Mar 87 07:24:07 GMT
Sender: usenet@jade.BERKELEY.EDU
Reply-To: jkh@violet.berkeley.edu(Jordan K. Hubbard)
Organization: University of California, Berkeley
Lines: 41
Keywords: Ultrix 2.0 config Vaxstation II Vaxstation 2000

I just got my Vaxstar (oops.. Vaxstation 2000 [ugh]..) booted up
(I swapped the RD/RX31 combo for an RD53) and now I'm trying to use
the "special" serial port. By "special", I'm refering to that
weird port that needs a special cable to plug into a standard DB-25 connector
(I don't even know what to call the 12 pin connector in the back of
the vax). The port on my Vaxstation II BA23 box works just fine on
major/minor 38, 0 (in fact, I'm using it right now to talk to this
machine). On the Vaxstation 2000, I don't quite know what the major/minor
is and I can only speculate that it's tty03, based on what DEC has
mentioned in passing. Under Ultrix 2.0-3A, when I kermit to this port
the system halts. This is very evil. Does anyone know what might be going
on?

BTW, has anyone gotten "newcsh" to work under 2.0 on an NFS file system?
Completion is really buggy if you're referencing a mounted file system
and some things don't work at all (like metacharacter expansion!). I get
expansion of metacharacters and the like just fine with /bin/csh, but of
course there's no filename completion.. I've used the 1.2 newcsh as well
as the version that comes on the 2.0 "Unsupported utilities" tape. The 1.2
version works sort of on ufs file systems, the DEC provided version just
exits.

Argh.

P.S. I've managed to cover a lot of ground so far in getting 2.0 up on the
Vaxstar as well as using the H4080 kludge-unit to network the thin-wire
ethernet to the "thick wire" used in the BA23 microvax box. I currently
have a BA23 uVax and a Vaxstar running 2.0-3A happily mounting each other's
file systems and putting X windows up on each other, etc. If anyone is trying
to get to a state similar to this, I can provide some insight to making it
all work.. Feel free to send me mail. Maybe we can trade answers, I have
more than a few questions of my own.

P.S.S. I hate the term "Vaxstation 2000". It sounds like a furniture
dealership. For those that were confused by my abrupt switch in terms,
I'm using the original "Vaxstar" designation. And will continue to do so.

						Jordan K. Hubbard
						U.C. Berkeley
						jkh@violet.berkeley.edu
						ucbvax!jkh