From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Can you specify a local IP or Interface to be used on a per NFS mount basis?
Date: Wed, 18 Jan 2006 23:24:58 -0500 [thread overview]
Message-ID: <1137644698.8864.8.camel@lade.trondhjem.org> (raw)
In-Reply-To: <43CF0768.60703@candelatech.com>
On Wed, 2006-01-18 at 19:28 -0800, Ben Greear wrote:
> > As David said, the place to fix it is in xs_bindresvport(), but there is
> > no support for passing this sort of information through the current NFS
> > binary mount structure. You would have to hack that up yourself.
>
> I can think of some horrible hacks to grab info out of a text file based
> on the mount point or some other available info...but if I actually
> attempted to do it right..would you consider the patch for kernel
> inclusion? Is it OK to modify the binary mount structure?
It is possible, yes: the binary structure carries a version number that
allows the kernel to distinguish the various revisions that the userland
mount program supports.
That said, the concensus at the moment appears to be that we should move
towards a text-based mount structure for NFS (like most of the other
filesystems have, and like NFSroot has) so I'd be reluctant to take
patches that define new binary structures.
Cheers,
Trond
next prev parent reply other threads:[~2006-01-19 4:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 23:10 Ben Greear
2006-01-19 0:48 ` Trond Myklebust
2006-01-19 2:21 ` Ben Greear
2006-01-19 2:29 ` David S. Miller
2006-01-19 3:24 ` Trond Myklebust
2006-01-19 3:28 ` Ben Greear
2006-01-19 4:24 ` Trond Myklebust [this message]
2006-01-20 4:26 ` Ben Greear
2006-01-20 13:52 ` Peter Staubach
2006-01-20 17:11 ` Ben Greear
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=1137644698.8864.8.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®