mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Peter Staubach <staubach@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Andrew Morton <akpm@linux-foundation.org>,
	nfsv4@linux-nfs.org, nfs@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [NFS] What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Fri, 5 Oct 2007 08:25:13 +0200	[thread overview]
Message-ID: <20071005082513.4b5a058c@poseidon.drzeus.cx> (raw)
In-Reply-To: <47054205.8000908@redhat.com>

On Thu, 04 Oct 2007 15:41:57 -0400
Peter Staubach <staubach@redhat.com> wrote:

> 
> I would agree.  The 64 bit fileids will only become visible when
> the server is exporting file systems which contain fileids which
> are bigger than 32 bits and then only when the application
> encounters these files.
> 

Or, as has been pointed out, when the server is not the Linux in-kernel
NFS server.

> Also, these 32-bit legacy applications are going to have a
> problem if they are ever run on a system which contains local
> file systems which expose the large fileids.
> 

Agreed. And I'd probably like a way around that as well. But local
files have never worked, NFS has. So removing it from NFS (where it is
more likely to occur IMO) would be a regression.

> It would be better to identify these applications and get them
> fixed.  The world is evolving and it is time for them to do so.
> 

Print a warning or something so that they can be found. Don't go
breaking systems left and right. People have better things to do than
to fix the build systems for ever program they use.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

  reply	other threads:[~2007-10-05  6:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 23:41 Trond Myklebust
2007-10-03 23:52 ` Jeff Garzik
2007-10-04  6:52 ` Pierre Ossman
2007-10-04 14:00   ` [NFS] " Trond Myklebust
2007-10-04 16:43     ` Pierre Ossman
2007-10-04 18:42       ` Andrew Morton
2007-10-04 19:16         ` Trond Myklebust
2007-10-04 19:41           ` Peter Staubach
2007-10-05  6:25             ` Pierre Ossman [this message]
2007-10-05 17:36               ` Trond Myklebust
2007-10-05 17:54                 ` Pierre Ossman
2007-10-04 19:59           ` Andrew Morton
2007-10-05  0:58             ` Trond Myklebust
2007-10-05 17:30     ` Valdis.Kletnieks
2007-10-05 17:52       ` Trond Myklebust
2007-10-05 18:00       ` Jeff Layton
2007-10-08  8:36         ` Greg Banks
2007-10-05 18:12       ` Jeff Layton
2007-10-07 22:56         ` David Chinner

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=20071005082513.4b5a058c@poseidon.drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4@linux-nfs.org \
    --cc=staubach@redhat.com \
    --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 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®