From: Wladimir Mutel <mwg@alkar.net>
To: 9fans@cse.psu.edu
Subject: [9fans] cpu/file/terminal server of my dream
Date: Mon, 26 Jun 2000 09:01:45 +0000 [thread overview]
Message-ID: <8j2rkd$267k$1@pandora.alkar.net> (raw)
Greetings,
Suppose I have basic Plan9 setup (9pcdisk).
I log on to its terminal server under my own user name.
How then do I give my file- and cpu-services to my unix colleagues,
provided they have 9term and wish to connect to my host to know some
more about Plan9 ?
How then do I make a secure file server of my local harddisk (with
some use restrictions for disk/kfscmd)? Now anybody can log on locally to
terminal server under any name and make anything with local filesystem
with kfscmd ! Nothing similar is observed for any unix installation,
why is it so insecure under Plan9 ?
I know I need to rebuild a kernel, but among different kernel
configurations I did not find one I want.
Really, what if I do not want, or simply am unable, to dedicate spare
headless machine for file serving (for example, since not having one) ?
I just have a strongest wish for single host to be file and cpu
server at the same time, and to become also a terminal server
whenever whoever wants to log on it locally (like X-server with xdm).
(and to log off it by stopping terminal server but keeping cpu and
file servers running). Is this my wish unreal under Plan9 ? May be
I should drop my sick enthusiasm and turn back to longly familiar unix?
Please explain me the Plan9 reality and may be help a little to
clear my thoughts.
--
mwg@alkar.net
next reply other threads:[~2000-06-26 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-26 9:01 Wladimir Mutel [this message]
2000-06-27 9:39 miller
2000-06-27 12:30 ` Wladimir Mutel
2000-06-28 15:56 miller
2000-06-28 16:13 ` Steve Kotsopoulos
2000-06-28 17:34 miller
2000-06-29 16:49 ` Wladimir Mutel
2000-06-28 18:40 rsc
2000-06-29 17:50 presotto
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='8j2rkd$267k$1@pandora.alkar.net' \
--to=mwg@alkar.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).