All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Garland <perlfs2@ericgarland.com>
To: nfs@lists.sourceforge.net
Subject: NFS support for PerlFS
Date: Fri, 02 May 2003 03:01:43 -0400	[thread overview]
Message-ID: <3EB217D7.6080706@ericgarland.com> (raw)

  I'm looking to add support to the PerlFS filesystem so
it can be exported using NFS.  From reading the
interface requirements it would seem the way to do
that would be to turn on the FS_REQUIRES_DEV flag in
the file_system_type structure that get's registered.
This works execpt I then need to pass a valid device
file into the mount command or mount doesn't work. 
The device I pass in doesn't have any bearing on the
filesystem that get's mounted which doesn't really make
much sense.

Is there any way of making the NFS server not
check the NFS_REQUIRES_DEV flag?

    -Eric



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2003-05-02  7:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3EB217D7.6080706@ericgarland.com \
    --to=perlfs2@ericgarland.com \
    --cc=nfs@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.