Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 8/7/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!ihnp4!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: More Eunice
Message-ID: <2816@ucbvax.ARPA>
Date: Thu, 25-Oct-84 14:16:26 EDT
Article-I.D.: ucbvax.2816
Posted: Thu Oct 25 14:16:26 1984
Date-Received: Fri, 26-Oct-84 09:13:28 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 23

From: *Hobbit* <AWalker@RUTGERS.ARPA>

We have just gotten the TWG TCP stuff working on our 780 [hoorayy!!].
The primary problem turned out to be a DOA Interlan board... Anyway,
while hacking around, I noticed that a lot of the man files are
constructed of lines of text separated by linefeeds [a la Unix, where
of course they came from in the first place].  Kind of confusing
to type out without a man processor that knows this.  The *other* thing,
is that any filename that is legal under Unix [something like 
inet-config.txt, which is over 9 chars in FN1 and has the "-"] and
is illegal under VMS gets translated to something like HSH0EERQ1.HSN.
There is evidently some tranlation algorithm whereby the bogus filename
is hidden in the encoding of this new name, and presumably some Eunice
routine that can unpack it again.  How exactly does this work?  Is there
extant a shell that runs under VMS/Eunice that will show you the ''real''
filename and deal with it that way?  Is there a simple reversal process
to find out the original filename?

This Eunice stuff looks like a teetery column of kludges, that should have
all fallen down long ago and convinced us to run Unix in the first place...

_H*
-------