| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Tue, 25 Feb 2003 14:42:02 -0800 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030225220628.GE710@frodo> |
| References: | <200302250911.h1P9BdOb874080@xxxxxxxxxxxxxxxxxxxxxxx> <20030225093429.GB27906@xxxxxxxxxxxxxxx> <1046169145.1367.1.camel@xxxxxxxxxxxxxxxxxxxxx> <20030225213710.GA22042@xxxxxxxx> <1046209159.31695.1991.camel@xxxxxxxxxxxxxxxxxxxx> <20030225215243.GB22195@xxxxxxxx> <20030225220628.GE710@frodo> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Wed, Feb 26, 2003 at 09:06:28AM +1100, Nathan Scott wrote: > The only thing that could go "wrong" is in xfsdump/restore at the > moment, and there are acceptable workarounds (IMO). xfsdump/restore are pretty important IMO these are not applications i'd like to see trivially broken... is it not possible to have userspace deal with both cases? it on'y needs to determine which namespace prefix is in use once and cache this result (somewhat like what glibc does in places) > Fortunately, tar and cp don't grok extended attributes yet sorry, bad example on my part i was complaining that important userspace tools all-of-a-sudden work differently depending on what kernel you boot... --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Bug 218] Probable mmap() bug that breaks cpp-3.2, Chris Wedgwood |
|---|---|
| Next by Date: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS, Nathan Scott |
| Previous by Thread: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS, Nathan Scott |
| Next by Thread: | Re: TAKE - attr-2.3.0, add trusted namespace into XFS, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |