From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Dr. Tilmann Bubeck" <t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
Cc: Steve Dickson <SteveD@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: Is order for "exportfs -r" and rpc.mountd important?
Date: Thu, 4 Dec 2008 09:35:53 -0500 [thread overview]
Message-ID: <20081204143553.GC3495@fieldses.org> (raw)
In-Reply-To: <200812041516.14114.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
On Thu, Dec 04, 2008 at 03:16:13PM +0100, Dr. Tilmann Bubeck wrote:
> It's very good that it is fixed in Fedora (my preferred distribution), but it
> is still wrong in SuSe (verified) and probably more.
>
> A better way would be to fix NFS and its utilities itself instead of fixing
> the distribution. This means, that the way the kernel and nfs-utils interact
> should be made more robust (see my posting before).
The problem of exportfs ignoring the uuid, at least, should be easy
enough to fix.
I'd start by looking for the relevant code in nfs-utils/utils/exportfs/
that passes the export entry down to the kernel and figure out what
mountd is doing that it's not.
--b.
next prev parent reply other threads:[~2008-12-04 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 14:41 Is order for "exportfs -r" and rpc.mountd important? Dr. Tilmann Bubeck
[not found] ` <200811281541.39272.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-11-28 16:05 ` Dr. Tilmann Bubeck
[not found] ` <200811281705.45087.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-12-03 17:25 ` J. Bruce Fields
2008-12-04 9:25 ` Dr. Tilmann Bubeck
[not found] ` <200812041025.02563.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-12-04 13:59 ` Steve Dickson
[not found] ` <4937E243.1080608-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-04 14:16 ` Dr. Tilmann Bubeck
[not found] ` <200812041516.14114.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-12-04 14:35 ` J. Bruce Fields [this message]
2008-12-04 14:43 ` Steve Dickson
2008-12-05 6:05 ` Neil Brown
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=20081204143553.GC3495@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org \
/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.