From: Neil Brown <neilb@cse.unsw.edu.au>
To: Steve Dickson <SteveD@RedHat.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>,
Chip Salzenberg <chip@pobox.com>, Andrew Morton <akpm@osdl.org>,
Rik van Riel <riel@RedHat.com>
Subject: Re: nfs-utils-1.0.5 is not backwards compatible with 2.4
Date: Mon, 4 Aug 2003 10:52:12 +1000 [thread overview]
Message-ID: <16173.44604.327927.223153@gargle.gargle.HOWL> (raw)
In-Reply-To: message from Steve Dickson on Friday August 1
On Friday August 1, SteveD@RedHat.com wrote:
> I see your point... I guess I didn't realize that the "nohide" option
> (that the user
> sees) has been using the NFSEXP_CROSSMNT define this whole time....
>
> And I also agree with you if somebody is directly using the bits instead of
> the "nohide" ascii representation they are on there own since there is no
> real export API per say....
>
> But just to make the clean up complete, wouldn't the attached patch be
> needed in the 2.4 kernel if nfs-utils-1.0.5 was going to be used?
It wouldn't hurt, but it certainly isn't needed (as it doesn't
actually change any bit of compiled code).
I will put it on my list to send for 2.4.23-pre
NeilBrown
next prev parent reply other threads:[~2003-08-04 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 17:12 nfs-utils-1.0.5 is not backwards compatible with 2.4 Steve Dickson
2003-07-31 18:23 ` Kernel 2.4 and 2.6 disagree about NFSEXP_CROSSMNT - upward incompatibility, please fix Chip Salzenberg
2003-07-31 22:05 ` Andrew Morton
2003-08-01 2:55 ` nfs-utils-1.0.5 is not backwards compatible with 2.4 Neil Brown
2003-08-01 12:43 ` Steve Dickson
2003-08-04 0:52 ` Neil Brown [this message]
2003-08-01 14:38 ` Chip Salzenberg
2003-08-04 0:55 ` 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=16173.44604.327927.223153@gargle.gargle.HOWL \
--to=neilb@cse.unsw.edu.au \
--cc=SteveD@RedHat.com \
--cc=akpm@osdl.org \
--cc=chip@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=riel@RedHat.com \
/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;
as well as URLs for NNTP newsgroup(s).