From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@9fans.net
Subject: Re: [9fans] P9p's mount(1) on linux
From: "Russ Cox" <rsc@swtch.com>
Date: Thu, 19 Jun 2008 19:21:10 -0400
In-Reply-To: <5d375e920806191329s6c88cd6fred9ff5ce9513b22d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20080619231951.6394F1E8C1F@holo.morphisms.net>
Topicbox-Message-UUID: c3a6d2fa-ead3-11e9-9d60-3106f5b1d025

>> A few p9p programs--acme, tapefs, vacfs--now
>> accept a -m option directing them to mount at a
>> particular place in the directory tree, via 9pfuse.
>> There is no option to mount via the Linux 9p module.
>
> Why not have them use p9p's mount(1)?

The code is trying to mount a file descriptor, and
the Linux 9P module provides no way to do that.
(In fact, that was the very first thing I asked for, years ago,
when I started trying to use v9fs, and to my knowledge,
it still hasn't happened.  Ron and Eric are focused on
replacing NFS, not building user-level file servers.)

I edited the code to call out to a non-existent mount9p
program before it invokes 9pfuse.  If you put a mount9p
in your path that can be invoked:

	mount9p - /mnt

to mount fd 0 onto /mnt, then the -m options will use
that instead of 9pfuse.  Perhaps one day v9fs will ship
with such a program.

Russ