9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fernan Bolando <fernanbolando@mailc.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Configuring NFS
Date: Sat, 13 Feb 2010 07:30:57 +0800	[thread overview]
Message-ID: <1d5d51401002121530t3df57af8w52889872de19584b@mail.gmail.com> (raw)
In-Reply-To: <7d3530220906021030w391ef36eg588f9feae05fa012@mail.gmail.com>

On Tue, Jun 2, 2009 at 5:30 PM, John Floren <slawmaster@gmail.com> wrote:
> Has anyone here successfully set up nfsserver to share Plan 9 files
> with Unix machines? The examples given in the man pages are rather...
> opaque. All I want to do is share one directory tree (/lib/music, in
> particular) with a number of independent Linux laptops and
> workstations.
>
> I'm looking into NFS because it seems that it has about the lowest
> barrier to entry of all the possible file-sharing methods. Any other
> suggestions would be appreciated.
>
> John

Hi John

I was wondering what happend to your attempt in setting up the
nfsserver? I am also trying to get it up because my client is using
openbsd and It doesnt have 9pfuse or v9fs support.

>From all the replies I seem to get a general idea of what needs to be done

I did this @the server
% aux/nfsserver -a tcp!thinktank -c /lib/ndb/nfs
% aux/pcnfsd
% aux/portmapper

@client
# mount -o soft,intr thinktank:thinktank /mnt/nfs
NFS Portmap: RPC: Program not registered

in /sys/log/nfs
thinktank Feb 13 07:07:05 get port
thinktank Feb 13 07:07:32 get port


It seems like I maybe having authentication issue, but not
partifularly sure where to check.
man nfsserver seems to indicate that the client should have a static
ip address is this correct?

the client are using dhcp to configure there ip. I am trying to add
static aliases to clients to see if will work, but wanted to check
everyone else's thought.


--
http://www.fernski.com



  parent reply	other threads:[~2010-02-12 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
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 [this message]
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=1d5d51401002121530t3df57af8w52889872de19584b@mail.gmail.com \
    --to=fernanbolando@mailc.net \
    --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).