Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!cunyvm!ndsuvm1!mtus5!eacons
From: EACONS@MTUS5.BITNET (Ernie Anderson)
Newsgroups: comp.sys.amiga
Subject: Getting workbench to mount a subdirectory...
Message-ID: <90036.140352EACONS@MTUS5.BITNET>
Date: 5 Feb 90 19:03:51 GMT
Organization: Computing Technology Services, Michigan Technological Univ.
Lines: 47

Our local user's group has gotten an account on one of the university's
sun workstations.  We then hooked our amiga up with dnet to it at
19200 baud.  Everything is fine except for a couple of questions that have
come up.

   1) When we mount NFS (as sun: :-) it mounts it as the root directory
   of the sun, rather than the local directory we have set up.  This isn't
   a problem from the CLI, but we would like to use Workbench (Just to show
   that it can be done, we ARE sitting next to a MACII).  The obvious
   problem is that when we open the sun: disk icon, there isn't anything in
   it because there aren't any icons in the root directory of the sun.  What
   we want to know is how to make a disk icon that when opened, shows the
   contents of the local directory.  Can this be done?

   2) There wasn't a mountlist entry example with the nfs-handler (no docs
   at all, actually, we just guessed at how to use it.) so we set the stack
   at 6000.  Is this much too big?  We don't have much memory, so every little
   bit counts.

   3) Finally, the amiga's idea of the path is funny from the nfs-handler.
   An example:
   mount sun:
   cd sun:/usr/local/homes/amiga
   cd
   sun:/usr/local/homes/amiga
   cd someprogs
   cd
   sun:/usr/local/homes/amiga/someprogs
   cd /
   cd
   sun:/usr/local/homes/amiga/someprogs/

   The above is from memory, so bear with me.  After the last step shown
   above, the actual directory is correct, if we do a dir, we get the contents
   of /usr/local/homes/amiga.  However, the path is really messed up.  If we
   do this using the WB1.3 shell, the prompt shows the current directory, and
   is affected the same way.  If we go into and out of several directories,
   the path just gets longer, and longer until the prompt takes up the whole
   line.  This is not a *problem*, in that it doesn't affect usage of the
   machine, but it is ugly, and hints at deeper problems.  Does anyone have
   an idea about this one?

Anyone having a clue about any of these problems can either post it or send
mail to any of the following addresses.  Thank You.

EJANDERS@MTUS5.BITNET
EACONS@MTUS5.BITNET