[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1191606750.6715.98.camel@heimdal.trondhjem.org>
Date: Fri, 05 Oct 2007 13:52:30 -0400
From: Trond Myklebust <trond.myklebust@....uio.no>
To: Valdis.Kletnieks@...edu
Cc: Pierre Ossman <drzeus-list@...eus.cx>,
Peter Staubach <staubach@...hat.com>, nfsv4@...ux-nfs.org,
Andrew Morton <akpm@...ux-foundation.org>,
nfs@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [NFS] What's slated for inclusion in 2.6.24-rc1 from the NFS
client git tree...
On Fri, 2007-10-05 at 13:30 -0400, Valdis.Kletnieks@...edu wrote:
> On Thu, 04 Oct 2007 10:00:50 EDT, Trond Myklebust said:
>
> > How about a boot/module parameter to turn it on or off?
> >
> > I don't see any point in having a sysctl for something like this: either
> > you have legacy applications or you don't. It is not something that you
> > switch off as you go off to lunch.
>
> How does Joe Sysadmin tell if he has an affected legacy app or not?
>
> (The obvious "try it and see what breaks" is a non-starter for many places,
> because you too easily end up in a loop of "enable it, find 4-5 show stoppers,
> turn it off, fix them, lather rinse repease". Been there, done that, got
> the tshirt - a project I got dragged into involves a large storage array that
> appears to insist on exporting 64-bit stuff, and a large farm of clients that
> are very 64-bit unclean....)
If you're unsure, then set the bloody boot parameter. That's what it is
for...
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists