info-vax@ucbvax.ARPA (10/26/84)
From: Art Berggreen <ART@ACC>
Requarding the recent EUNICE inquiries:
EUNICE knows about both UNIX style files (LFs for record seperators)
and the various ways VMS maintains files. Most of the files that
came from UNIX (e.g. .h files) are still in UNIX format and carry
no VMS carriage control information. If you try to print these under
VMS all you get for carriage control is LFs. The EUNICE I/O routines
know when to supply proper carriage control for printing devices
(i.e. ttys, line printers, etc.). There are two utilities in /etc
(SYS$DISK:[EUNICE.ETC]) for converting back and forth between UNIX
and VMS formats. "/etc/unixtovms" converts from UNIX format to VMS
format and "/etc/vmstounix" the other way.
VMS maintains filenames only in upper case, has a limited set of
legal characters and only nine character names with a three character
extension (big changes here in V4). UNIX supports 14 character names
(longer in 4.2), case is significant and a larger set of legal characters.
EUNICE will translate any filename legal in VMS to the lowercase equivalent
under UNIX and vice versa. Thus all VMS filenames are readable under
EUNICE. Any UNIX filenames that can't fit the VMS mold are converted
to an encoded filename using a hashing algorithm (the details of which
I don't know, maybe TWG will tell you). The resultant filename has the
following VMS format: HSH0vwxyz.HSH, where vwxyz are derived from hashing
the UNIX filename. Another file is created named HSH0vwxyz.HSN which
contains the UNIX filename and the VMS HSH0vwxyz.HSH filename. The
.HSN files can be examined under VMS to find out what UNIX filenames they
represent. The hashing seems to add significant overhead to file access.
TARing a 4.2 tape into EUNICE seems to take much longer than even a
TS11 should cause.
We have found DCL foreign commands to be an excellent way of running
handy UNIX programs from a VMS environment (e.g. VI, MORE, GREP, FINGER,
etc.). For example: $ VI :== $_DUA0:[EUNICE.USR.UCB]VI VI<cr> allows
VI to be invoked from DCL.
Also make sure you set your process quotas as indicated in the EUNICE
documentation, especially PRCLIM (subprocess limit) as EUNICE tends to
keep trees of subprocesses laying around for reuse in order to avoid
the time required for subprocess creation. If you exhaust your quota
things will often just seem to hang.
Art Berggreen
Advanced Computer Communication
<Art@ACC.ARPA>
------info-vax@ucbvax.ARPA (02/19/85)
From: Ronald A. Jarrell <JARRELLRA@VPIVAX3.BITNET>
Anyone have any info on Eunice vs. 4.0? Things like:
1) Does it break? (I'm sure it wil, but would love to be surprised)
2) What plans does anyone have for coping with it other than
not installing 4.0
3) Any word on an update to Eunice fixing it if it does break?
4) Anyone found anything better?
-Ron Jarrell
Va Tech