9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] afd in mount(2)
Date: Wed, 10 Jul 2002 07:46:21 +0100	[thread overview]
Message-ID: <9e11ad93789992d30b783e65349806e8@caldo.demon.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 734 bytes --]

venti is currently optional--i don't use it yet myself--and factotum looks
after itself (you'll see a few different prompts, but otherwise it
doesn't require care and attention).  one difference for
authentication is that authdom= auth= pairs are needed in
/lib/ndb/local for each authentication domain you need.
	auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
for instance.

if you've written your own file servers, you'll have some work to do.
there are big differences in the C libraries and programming
interface.  see /sys/doc/release4.ps and /sys/doc/prog4.ps
to see where to start.

the file server kernel source is a little more convenient for configuration
compared to the previous release.

[-- Attachment #2: Type: message/rfc822, Size: 1671 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] afd in mount(2)
Date: Wed, 10 Jul 2002 15:28:32 +0900
Message-ID: <20020710062910.97BD719A08@mail.cse.psu.edu>

>see /sys/doc/auth.ps for more information.

Thanks a lot.

I remind now someone also recommended to read this document.
It'll take some more time to me to introduce new networked Plan 9
system here.   factotum, venti, .. anything else?

Kenji-- hate using anything beyond my comprehension  :-)

             reply	other threads:[~2002-07-10  6:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10  6:46 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-10  7:01 okamoto
2002-07-10  6:28 okamoto
2002-07-10  6:04 forsyth
2002-07-10  5:45 okamoto

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=9e11ad93789992d30b783e65349806e8@caldo.demon.co.uk \
    --to=forsyth@caldo.demon.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).