All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: RFC: mount.nfs
Date: Fri, 27 Aug 2004 20:24:53 +0200	[thread overview]
Message-ID: <20040827182452.GA20962@suse.de> (raw)
In-Reply-To: <1093630421.5758.42.camel@lade.trondhjem.org>

On Fri, Aug 27, 2004 at 02:13:42PM -0400, Trond Myklebust wrote:
> Note though that pmap_getmaps() is not supported on legacy portmappers
> (I think someone complained that their AIX system broke). This is why

In what way do these legacy portmappers fail? Does the PMAP_DUMP actually
kill the portmapper? If we are able to safely identify broken portmappers,
I assume we can fall back to enumerating the available versions by
sending a GETPORT request with version 0, and loop over that range.

I can easily put all that stuff into a library, no problem.

> the rewrite that is in Fedora Core 2 goes to such lengths to actually
> "ping" the server.

I wasn't aware that Redhat already had a rewrite. I'll take a look.

> Also note that ideally, we want to make stuff like this as part of a
> backend library, then have 3 different programs:
>   mount.nfs2
>   mount.nfs3
>   mount.nfs4
> that can be called when the user does
> 
>     mount -t nfs -onfsvers=%d

That's fine with me. But I think we still need a mount.nfs, because
we need to handle the case where the user doesn't specify an NFS
version. Calling all mount.nfsX apps in turn may be a bit awkward.

> The reason why I want to split out nfs2 from the nfs3 mount is that at
> some point in the near future, I'd like to change the filesystem
> registration to create 'struct file_system_type' entries for NFSv2 and
> NFSv3. That will enable us to
> 
>    a) clean up the struct nfs_mount to get rid of all that "struct
> socket", version 1 legacy crap

We can do that now, if we drop the requirement of making the struct
backward compatible. We already deduce the kernel API version by
looking at the kernel release number, so that can be done safely.

>    b) be able to enumerate exactly which NFS versions the kernel has
> been compiled to support by using 'cat /proc/filesystems'.

Olaf
-- 
Olaf Kirch     |  The Hardware Gods hate me.
okir@suse.de   |
---------------+ 


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-08-27 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 14:15 RFC: mount.nfs Olaf Kirch
2004-08-27 18:13 ` Trond Myklebust
2004-08-27 18:24   ` Olaf Kirch [this message]
2004-08-27 19:16     ` Trond Myklebust
2004-08-28 17:21 ` Steve Dickson
2004-08-28 18:21   ` Olaf Kirch

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=20040827182452.GA20962@suse.de \
    --to=okir@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.