From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: DENIEL Philippe <philippe.deniel@cea.fr>,
Tomasz Chmielewski <mangoo@wpkg.org>,
linux-nfs <linux-nfs@vger.kernel.org>,
tigran mkrtchyan <tigran.mkrtchyan@desy.de>
Subject: Re: !
Date: Wed, 14 Nov 2012 15:38:12 -0500 (EST) [thread overview]
Message-ID: <132199707.99.1352925492348.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1450527224.97.1352925325502.JavaMail.root@thunderbeast.private.linuxbox.com>
Hi Trond,
I think your point that discussion of alternative ways of doing things which might ultimately be standardized reflects lack of understanding of the concept of standardization is ... a non-sequitur.
I did state that the standard doesn't benefit from restricting the ability of implementations and applications from evolving new metadata conventions entirely above the file system. This claim is in no way radical, it's how everyone uses the file system already.
Since I haven't violated any rule of netiquette or convention of polite discussion generally, forgive me for not going away.
Regards,
Matt
----- "Trond Myklebust" <Trond.Myklebust@netapp.com> wrote:
> > You've said that xattrs and named attributes are completely
> different, but notwithstanding that, there seems to be logically quite
> a bit of overlap. Clearly, the fact that the NFS protocol treats
> named attributes as subfiles is a detail that the client need not
> expose to applications. It also seems as if an xattr interface is
> convenient for interacting with at a subset of named attributes (ones
> with tractable length names/values). I mean, as I note, this is the
> proplist, and that has been a very successful interface in a lot of
> systems, going back a -long- ways.
>
> NO! GO AWAY!!!!
>
> Seriously, if you don't understand the concept of a standard, then go
> away!
>
> Trond
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next parent reply other threads:[~2012-11-14 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1450527224.97.1352925325502.JavaMail.root@thunderbeast.private.linuxbox.com>
2012-11-14 20:38 ` Matt W. Benjamin [this message]
2012-11-14 21:03 ` ! Myklebust, Trond
2012-11-14 20:13 xattr support in NFS? Matt W. Benjamin
2012-11-14 20:24 ` ! Myklebust, Trond
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 14:44 àúí îöìîéí àú äö'÷éí? àé ãé ôé îåöøé æéäåé àì÷èøåðééí
2007-10-22 6:47 àé ãé ôé îåöøé æéäåé àì÷èøåðééí
2007-10-01 2:45 äæîï ùìê é÷ø? àé ãé ôé îåöøé æéäåé àì÷èøåðééí
2007-09-21 13:14 àé ãé ôé îåöøé æéäåé àì÷èøåðééí
2007-09-19 11:37 äæîï ùìê é÷ø IDP
2007-08-25 19:05 çñåê æîï åèòåéåú I.D.P
2007-08-17 17:57 àðé ìà æåëø àú ëì äôøèéí àé ãé ôé
2006-08-17 20:14 îçùá ëó éã áîúðä áæ÷ ìòñ÷éí
2006-07-23 20:20 øåöä ìäøùéí àú äì÷åç ùìê ? ìéàú
2006-07-04 12:43 øåöä ìäéåú îìê ìéåí àçã ? ìéàú
2003-07-07 16:38 (±¤°í)ÀÎÅͳݺξ÷ ±è¿øº¹
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=132199707.99.1352925492348.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=philippe.deniel@cea.fr \
--cc=tigran.mkrtchyan@desy.de \
/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