Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!rutgers!bellcore!texbell!camdev!sscott
From: sscott@camdev.UUCP (Steve Scott)
Newsgroups: comp.mail.elm
Subject: Help with ELM on Apollo BSD 4.2
Message-ID: <185@camdev.UUCP>
Date: 17 Apr 89 13:46:12 GMT
Reply-To: sscott@camdev.UUCP (Steve Scott)
Distribution: na
Organization: Motorola, Inc.  Ft. Worth, TX
Lines: 38

I have just received the newest version of ELM and I think that it is
great!  

Now, I have two flavors of UNIX (HP/UX and DOMAIN/IX on an Apollo DN3500).
The HP/UX version works like a champ (no surprise there, eh, Dave Taylor?)

The Apollo version works OK with a minor bug (which can be fixed by
running ELM in a vt100 window)

The bigger problem is this:

BTW: I am using BSD 4.2 (Apollo version 9.5) of DOMAIN/IX.  I am HOPING!!
that version 10.1 fixes this stuff up.  I HATE IT when I have to use
proprietary OS's

The Apollo distributed file system references everything by a system root
(//).  So, for example, home directories are of the sort //{node}/users/foo,
etc.  Now, ELM when finding a person's home directory (from /etc/passwd,
I presume ;-)), strips the initial / leaving /{node}/users/foo, which
does NOT exist in the file system.  I know that a call to access is failing
which causes the returned error.  And I know that I can strip off the
//node part in init.c.  But, if I do that, then I can only run elm from
my node.

Question is:  Has anybody turned in fixes or mentioned the proper sources
to modify to allow ELM to work properly on Apollos?  Or, a bigger question
is, how are these sort of things handled routinely in the Apollo world.
I feel quite certain that this thing happens all of the time (that is,
reading the home directory from /etc/passwd).

Any help would appreciated

Thank you very much in advance!


-- 
Steve Scott            UUCP: {killer|texbell}!camdev!sscott
Motorola, Inc.         Telephone : 1-817-232-6317