From: Tim Newsham <newsham@lava.net>
To: 9fans@cse.psu.edu
Subject: [9fans] newbie question #2
Date: Mon, 19 Jul 2004 12:10:07 -1000 [thread overview]
Message-ID: <Pine.BSI.4.58.0407191206390.9843@malasada.lava.net> (raw)
(how many newbie questions do I get? I hope that doesn't count as one).
I setup a server that serves bootp/tftp/auth/fs/cpu. I then
setup a diskless client. Most things seem to be in working
order now. I notice though that if I "cpu" in to the cpu
server from a terminal as myself, I can acme fine, but if
I "cpu" in as "bootes" (the fs owner), I have no /dev/draw
and I can't run acme (or other gui apps). Why is that?
Shouldn't my /dev/draw from my terminal be preserved in
the namespace of the new shell on the server? Am I doing
something wrong? If not, is there a workaround?
(yes, I am aware of "ed", and am comfortable using it when
I have to. I am more interested in knowing what is going
on here than in getting acme running).
Tim N.
next reply other threads:[~2004-07-19 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 22:10 Tim Newsham [this message]
2004-07-19 22:21 ` andrey mirtchovski
2004-07-19 23:05 ` rog
2004-07-19 23:08 ` andrey mirtchovski
2004-07-21 1:21 ` [9fans] gmake in ape Tim Newsham
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=Pine.BSI.4.58.0407191206390.9843@malasada.lava.net \
--to=newsham@lava.net \
--cc=9fans@cse.psu.edu \
/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).