From: Thomas Riemer triemer@babbitt.bernstein.com
Subject: Next problem
Date: Sun, 7 Apr 1996 16:35:01 -0400 [thread overview]
Message-ID: <19960407203501.zanK1-u5CFhkyZ2nHXVmXkdQ6Dm9Dc-p7uGDuplgG14@z> (raw)
So at this point the cpu service seems to half-way work.
That is to say, I can log in to the cpu server as my self -
and I can run things that talk to /dev/cons - but it
doesn't actually mount the fileserver...
I actually end up having to different directories... one on
the fileserver that I'm connected to when I boot the terminal up,
and one on the cpu server.
I was under the impression that the cpu service automatically mounted
the correct file server when one logged into it... so that the
user files would be the same regardless of location... Am I just
hallucinating here?
-Tom
---- Where theory and reality meet.
---- Thomas Riemer, tom@rockvax.rockefeller.edu
reply other threads:[~1996-04-07 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19960407203501.zanK1-u5CFhkyZ2nHXVmXkdQ6Dm9Dc-p7uGDuplgG14@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).