From: Emmanuel Florac <eflorac@intellique.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] enable inode64 by default when possible
Date: Wed, 10 Feb 2010 21:42:16 +0100 [thread overview]
Message-ID: <20100210214216.0ab263fd@galadriel.home> (raw)
In-Reply-To: <4B7313D9.9020603@sandeen.net>
Le Wed, 10 Feb 2010 14:15:21 -0600 vous écriviez:
> > But doesn't it cause problems specially for NFS sharing ?
> >
>
> For some clients, yes - as do other NFS servers.
It would be nice to mention which one... At least it would be good to
know at least approximately which releases of the main Unix clients
(Linux, Solaris, OS X, BSDs, HP/UX, AIX) are compatible.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-10 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 19:32 [PATCH] enable inode64 by default when possible Eric Sandeen
2010-02-10 20:04 ` Emmanuel Florac
2010-02-10 20:15 ` Eric Sandeen
2010-02-10 20:42 ` Emmanuel Florac [this message]
2010-04-09 22:01 ` Alex Elder
2010-04-10 2:37 ` Stan Hoeppner
2010-04-10 3:34 ` Eric Sandeen
2010-04-12 6:21 ` Dave Chinner
2010-04-13 6:35 ` Stan Hoeppner
2010-04-14 6:57 ` Andi Kleen
2010-04-12 6:12 ` [RFC, PATCH] inode64 feature bit (was Re: [PATCH] enable inode64 by default when possible) Dave 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=20100210214216.0ab263fd@galadriel.home \
--to=eflorac@intellique.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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