From: matt <matt@proweb.co.uk>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] cpu server as FS
Date: Fri, 4 May 2001 02:23:36 +0100 [thread overview]
Message-ID: <4624546606.20010504022336@proweb.co.uk> (raw)
Hullo 9fans,
urghh 2.20am
I've spent the evening setting up my first auth server.
it works fine i think but of course I made it look for a file server
it can't find (itself!).
The wiki page says :
"A set of patches to kfs exists to make it act as a network file server,
so that you could use one machine to support the network rather than
needing two."
Did Fermat write that line? How can I find these mysterious patches?
Sorry if thay are somewhere obvious but like I say it's late & I'm
tired and I'm hoping help will be at hand when I wake up to carry on.
--
matt mailto:matt@proweb.co.uk
next reply other threads:[~2001-05-04 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 1:23 matt [this message]
2001-05-04 1:49 Russ Cox
2001-05-04 8:53 Richard Miller
2001-05-08 8:30 ` Alexander Povolotsky
2001-05-08 13:22 rob pike
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=4624546606.20010504022336@proweb.co.uk \
--to=matt@proweb.co.uk \
--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).