9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Configuring NFS
Date: Tue,  2 Jun 2009 16:30:37 -0700	[thread overview]
Message-ID: <7d3530220906021630x59490e1ao8f4049f95295c676@mail.gmail.com> (raw)
In-Reply-To: <509071940906021622p3a7fa8acp846ae7a70504e974@mail.gmail.com>

On Tue, Jun 2, 2009 at 4:22 PM, Anthony Sorace <anothy@gmail.com> wrote:
> "none" does not (normally) give you read-only access; if something is
> world-writable, none will be able to write it. but getting read-only
> is pretty easy; see exportfs(4) and the files which use it in
> /rc/bin/service. from emory, i'd say "exec /bin/exportfs -Rr
> /lib/music" would do what you want.
>
> i've used nfsserver to provide access to a bunch of different types of
> unix hosts, but it has been a while. i just spent a few minutes right
> now trying with OS X and a remote plan9 server with no joy, but i'm
> not convinced i don't have a nat being disruptive.
>
> as far as the examples in nfsserver(8) go:
> "ivy" is a machine which responds to 9fs and exports a namespace
> containing /etc/passwd and /etc/group; it is most likely a unix system
> running u9fs or similar. /lib/ndb/nfs contains a 9fs command to mount
> ivy, so you can look at the live passwd and group files. if you'd
> rather not, or are unable to, get u9fs working on some authoritative
> unix system, you can copy or create a representative set locally (say,
> /lib/ndb/unix.passwd) and change the last two file names in the
> /lib/ndb/nfs example to point to those.
>
> "edith" and "yoshimi" are just 9p servers, most likely plan9 machines.
> passing them in the -a argument to nfsserver means that nfs clients
> attempting to mount the machines will have those two "shares" to pick
> from.
>
> i believe the example becomes inconsistent here; i think edith/yoshimi
> should match bootes/fornax. so if you had run the example as given
> here, you'd want to run "/etc/mount -o soft,intr eduardo:ivy /n/ivy"
> on your unix system. i forget whether the "share" ("ivy") needs to
> match the exact string given to -a ("tcp!ivy") or if just the hostname
> is okay.
>
>

What exactly is the purpose of the passwd and group files?

John
--
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba



  reply	other threads:[~2009-06-02 23:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 17:30 John Floren
2009-06-02 17:35 ` Roman V. Shaposhnik
2009-06-02 18:03   ` John Floren
2009-06-02 18:19     ` Roman V. Shaposhnik
2009-06-02 18:34       ` John Floren
2009-06-02 18:49         ` Eric Van Hensbergen
2009-06-02 19:57           ` John Floren
2009-06-02 23:22             ` Anthony Sorace
2009-06-02 23:30               ` John Floren [this message]
2009-06-02 23:41                 ` Anthony Sorace
2009-06-02 23:51                   ` John Floren
2009-06-03  3:18                     ` Anthony Sorace
2009-06-03  3:29         ` J.R. Mauro
2009-06-09 16:48         ` Roman V Shaposhnik
2009-06-09 16:48           ` J.R. Mauro
2009-06-11  5:47           ` Ethan Grammatikidis
2009-06-02 18:19 ` Steve Simon
2010-02-12 23:30 ` Fernan Bolando
2010-02-12 23:58   ` geoff

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=7d3530220906021630x59490e1ao8f4049f95295c676@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --cc=9fans@9fans.net \
    /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).