| To: | Nathan Scott <nathans@xxxxxxx>, Alexander Viro <viro@xxxxxxxxxxxx>, Andi Kleen <ak@xxxxxxx>, Andreas Gruenbacher <ag@xxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [RFC][PATCH] VFS interface for extended attributes |
| From: | Daniel Phillips <phillips@xxxxxxxxxxxxxx> |
| Date: | Mon, 3 Dec 2001 01:07:13 +0100 |
| In-reply-to: | <20011116101800.A632931@wobbly.melbourne.sgi.com> |
| References: | <Pine.LNX.4.21.0111121152410.14344-100000@moses.parsec.at> <20011114230134.A5739@lynx.no> <20011116101800.A632931@wobbly.melbourne.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Hi, sorry for jumping into this a little late, but... On November 16, 2001 12:18 am, Nathan Scott wrote: > > What is the distinction between "set" and "replace" or "set" and "create"? > > +#define EA_CREATE 0x0001 /* Set the value: fail if attr already exists */ > +#define EA_REPLACE 0x0002 /* Set the value: fail if attr does not exist */ > > Whereas "set" is simply set the named attribute value, creating the > attribute if need be, replacing the value if the attribute exists, > and then return success. What is the purpose of these distinctions? Does anyone rely on them? Do such distinctions exist in an existing implementation? Thanks. Daniel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS In 2.5, Eric Sandeen |
|---|---|
| Next by Date: | Re: [RFC][PATCH] VFS interface for extended attributes, Nathan Scott |
| Previous by Thread: | Re: anaconda-runtime-7.2-11XFS problem, Jérôme Tournier |
| Next by Thread: | Re: [RFC][PATCH] VFS interface for extended attributes, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |