On Tue, Jun 2, 2009 at 11:19 AM, Roman V. Shaposhnik <r...@sun.com> wrote:
> On Tue, 2009-06-02 at 11:03 -0700, John Floren wrote:
>> On Tue, Jun 2, 2009 at 10:35 AM, Roman V. Shaposhnik <r...@sun.com> wrote:
>> > On Tue, 2009-06-02 at 10:30 -0700, John Floren 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 used it in combination with Solaris.
>>
>> Do you still have the configuration?
>
> I might. For Solaris NFS was *the* only choice. For Linux I have
> abandoned NFS approach in favor of native 9P. You should be
> aware of the fact that nfsserver can only speak NFS v.2 which
> is *really* old.
>
>> I'm looking at the man page for
>> nfsserver but wondering what the machine 'ivy' does, and what exactly
>> 'pie' and 'yoshimi' are doing, etc.
>
> If you have practical questions -- feel free to ask them. I'll try
> to dig bits and pieces of my Solaris setup for you later this week.
> So far, I can tell you this much: nfsserver is NFS to 9P translator.
> Thus you can hide a whole bunch of 9P-aware services behind a single
> nfsserver by specifying multiple -a options (in fact these 9P
> services don't even have to be remote machines). Each individual -a
> entry will become a single NFS export share in its own right (visible
> via showmount -e).
>
> So, when you see something like
> aux/nfsserver –a tcp!pie –a tcp!yoshimi
> all this means is that we are creating 2 NFS shares pie and yoshimi
> on a single NFS server.
>
>> >> 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.
>> >
>> > Whether or not to use NFS depends greatly on what is on the other end.
>> > What kind of UNIX?
>> >
>>
>> Like I said, it's a collection of Linux machines, mostly running
>> Debian, Ubuntu, and Redhat.
>
> In that case why not use FUSE and 9P? This will also let you mount
> more easily from a non-root accounts.
>
> Thanks,
> Roman.
>
I'd like to use the 9p mounting available in Linux, but it doesn't
seem to work in this case.
I try "mount -t 9p glenda /mnt" (glenda is my cpu/file server) and get:
mount: wrong fs type, bad option, bad superblock on glenda,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so
If I do "mount -t 9p 192.168.18.180 /mnt", using the file server IP, I just get
mount: permission denied
But dmesg shows "[88617.144804] p9_errstr2errno: server reported
unknown error cannot attach as none before authentication", ONLY when
I use the IP address--nothing appears when I use the /etc/hosts alias
"glenda".
What am I missing?
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
