From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm and fileserver
Date: Sat, 20 Sep 2003 10:15:36 -0400 [thread overview]
Message-ID: <49cc09c4a0e723a3cac057a2809f5ae9@plan9.bell-labs.com> (raw)
In-Reply-To: <af0672256aac854266527fc26e1d9951@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
Argh! I know I'm crazy when I continually contradict my own email messages.
cpu does its own newns so giving a -n namespace to aux/listen won't work.
However, you could do the appropriate binds in the cpu case of your profile
to see whatever namespace you'ld like:
switch($service){
case terminal
...
case cpu
bind -a /mnt/term/mnt/wsys /dev
bind /mnt/term/dev/cons /dev/cons
bind /mnt/term/dev/consctl /dev/consctl
bind -a /mnt/term/dev /dev
srv fileserver
mount /srv/fileserver /n/fileserver
bind /n/fileserver/usr /usr
bind /n/fileserver/sys /sys
...
}
None of this will result in a direct connection from the machine you run
drawterm on to the fileserver. It'll always be filtered through cpu.
[-- Attachment #2: Type: message/rfc822, Size: 7401 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 245 bytes --]
You could do what rsc suggested, but if you want your auth server on a stand alone
machine and it is also the cpu server, you could have whatever name space you want
when you cpu into the cpu server just by using the -n argument on aux/listen.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 5096 bytes --]
[-- Attachment #2.1.2.1.1: Type: text/plain, Size: 189 bytes --]
You don't, its just a cpu connection to a cpu server.
Drawterm isn't an emulation of a plan 9 terminal, just
an emulation of a plan 9 terminal at the end of a connection
to a cpu server.
[-- Attachment #2.1.2.1.2: Type: message/rfc822, Size: 2902 bytes --]
From: Matthias Teege <matthias@mteege.de>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] Drawterm and fileserver
Date: Sat, 20 Sep 2003 08:59:45 +0200
Message-ID: <86smms9c7y.fsf@gic.mteege.de>
Moin,
with a lot of help from the 9fans my Plan9 network is now up and
running. I have a cpu/auth- and a fileserver and I can remote boot
terminals. After booting the terminals they are using the fileserver
as expected.
I also play with drawterm. I can connect to the cpu/auth server,
authenticate a user and login. But if I login with drawterm, the
filesystem isn't mounted from the fileserver but from the cpu/auth
server.
How do I tell drawterm to work like the remote booted terminal?
I also have s problem with «9fs dump». This command gives me
«mount: mount /n/dump: attach -- bad specifier». 9fs batida works
and I can also mount the dump with:
srv -q il!batida
mount /srv/il!batida /n/dump dump
Many thanks
Matthias
--
Matthias Teege -- http://www.mteege.de
make world not war
PGP-Key auf Anfrage
next prev parent reply other threads:[~2003-09-20 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 13:50 David Presotto
2003-09-20 14:07 ` David Presotto
2003-09-20 14:15 ` David Presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-20 6:59 Matthias Teege
2003-09-20 7:08 ` Russ Cox
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=49cc09c4a0e723a3cac057a2809f5ae9@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).