From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu/auth/fs
Date: Wed, 31 Oct 2001 23:30:45 -0500 [thread overview]
Message-ID: <20011101043102.0E609199E7@mail.cse.psu.edu> (raw)
i believe the kfs patches to allow a cpu server to also act as a file server
(minus dumps, of course) are in the normal distribution now (i'm using
them, and i _think_ that's where i got them from). it's pretty easy (the fs
part is, anyway). set up the cpu server as normal, and just add the lines:
disk/kfscmd 'listen il!*!17008'
disk/kfscmd 'listen tcp!*!564'
to /rc/bin/cpurc, and it'll listen on the normal file server ports and serve
authenticated access to your kfs file system.
i _think_ that's what you're asking for. auth servers can be a bit
complicated to set up, but there isn't really anything _tricky_ about them,
and i think the documentation's sufficient. if you run into problems there,
let us (or me) know.
ア
next reply other threads:[~2001-11-01 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 4:30 anothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 3:27 [9fans] 3COM NIC jmk
2001-11-01 4:20 ` [9fans] cpu/auth/fs Dharani Vilwanathan
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=20011101043102.0E609199E7@mail.cse.psu.edu \
--to=anothy@cosym.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).