From: Stephen Wynne <stevemw@mindspring.com>
To: Matthias Teege <matthias@mteege.de>, 9fans@cse.psu.edu
Subject: Re: [9fans] Setup the fileserver
Date: Fri, 11 Aug 2000 04:27:14 -0400 [thread overview]
Message-ID: <200008110827.EAA12671@fuji.rem.cs.cmu.edu> (raw)
In-Reply-To: Matthias Teege <matthias@mteege.de> 's message of "Fri, 11 Aug 2000 08:11:09 +0200." <200008110611.IAA29939@moon.mteege.de>
> Are there manuals out there for setup an fileserver?
Guten Tag, Herr Teege.
Reading from "Starting up the file server" at
ftp://ftp.dbsystems.com/pub/plan9/install.html helped me
see the order of commands documented elsewhere.
I recommend reading Ken's "The Plan 9 File Server" paper
at http://plan9.bell-labs.com/sys/doc/fs/fs.html -- more
than once.
That refers you to the fsconfig(8) manual page at
http://plan9.bell-labs.com/magic/man2html/8/fsconfig
and the more general fs(8) manual page at
http://plan9.bell-labs.com/magic/man2html/8/fs
It helps to remember that there is nothing (as far as I know) on the
file server once you've booted. You need to mount a filesystem from it
to populate its /adm/users file, for example. You can create files and
directories from the fileserver's console.
You may want to use a serial console while you work: Set up plan9.ini
with these entries and connect to another system:
console=0 <== COMA on my plan9pc server.
baud=38400
Both video/keyboard and serial input/output work now.
Once you've got something up, on a Plan 9 terminal do:
term% srv il!serverhostname <== connect
term% mkdir /n/.partitionname <== a place to mount the service.
term% mkdir /n/partitionname <== a place to bind it.
term% bind -c /n/.partitionname /n/partitionname
term% cd /n/partitionname
Cat out /bin/9fs for examples.
Viel Gluck!
prev parent reply other threads:[~2000-08-11 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-11 6:11 Matthias Teege
2000-08-11 8:27 ` Stephen Wynne [this message]
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=200008110827.EAA12671@fuji.rem.cs.cmu.edu \
--to=stevemw@mindspring.com \
--cc=9fans@cse.psu.edu \
--cc=matthias@mteege.de \
/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).