| To: | Chris Wedgwood <cw@xxxxxxxx> |
|---|---|
| Subject: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Wed, 26 Feb 2003 09:06:28 +1100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030225215243.GB22195@xxxxxxxx> |
| References: | <200302250911.h1P9BdOb874080@xxxxxxxxxxxxxxxxxxxxxxx> <20030225093429.GB27906@xxxxxxxxxxxxxxx> <1046169145.1367.1.camel@xxxxxxxxxxxxxxxxxxxxx> <20030225213710.GA22042@xxxxxxxx> <1046209159.31695.1991.camel@xxxxxxxxxxxxxxxxxxxx> <20030225215243.GB22195@xxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
On Tue, Feb 25, 2003 at 01:52:43PM -0800, Chris Wedgwood wrote: > On Tue, Feb 25, 2003 at 03:39:19PM -0600, Steve Lord wrote: > > > Yep, unless you use the environment variable Nathan mentioned in his > > original message (I do not have it here, but I seem to remember him > > mentioning one for backwards compatibility). > > Yes. I saw that. IMO it sucks. > > I means I have to conciously check my kernel version and bugger about > or else things break. The only thing that could go "wrong" is in xfsdump/restore at the moment, and there are acceptable workarounds (IMO). > Great. > > Imagine if tar or cp worked this way... Fortunately, tar and cp don't grok extended attributes yet, so we're trying to make sure we use generic names that have meaning on other filesystem types too before this becomes a problem for those tools. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS, Nathan Scott |
|---|---|
| Next by Date: | Re: [Bug 218] Probable mmap() bug that breaks cpp-3.2, Chris Wedgwood |
| Previous by Thread: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS, Chris Wedgwood |
| Next by Thread: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS, Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |