Re: File attribute problem

"Justin C. Walker" <[email protected]>
Newsgroups gmane.comp.macosx.admin
Message-ID <[email protected]>
On Aug 1, 2011, at 23:36 , LuKreme wrote:

> Justin C. Walker <[email protected]> squaked out on Mon 01-Aug-2011 22:55
>> On Aug 1, 2011, at 21:13 , Richard Peskin wrote:
>> 
>>> I have a volume where all the files have the following type attribute:
>>> drwxr-xr-x@  11 rpeskin  staff      374 Jan 13  2010 Snow Leopard
>>> 
>>> The "@" attribute is a real problem; it prevents write access to the file or Volume unless admin authorization is supplied. I have no idea how this "@" got there; the volume (a disk partition) was created in the usual way with diskutil. How can I get rid of these "@" attributes?
>> 
>> I don't think the "@" decorator prevents any access by itself.  The "@" decorator in 'ls' output is explained in the man page (the 'file' has extended attributes).  To see what attributes are present, use the 'xattr' command (use "xattr -h" to see what the command does).
> 
> xattr is not needed, it’s functionality is part of the standard ls command and has been since 10.5, iirc. Certainly 10.6.
> 
> ls -l@ <file> will show the extended attributes.
> 
> $ ls -lnd@ bin
> drwxr-xr-x@ 62 501  20  2108 Jul 21 23:30 bin
> 	com.apple.FinderInfo	  32 
> 
> ~/ $ ls -lnd@ bin/sixsyn
> -rwx------@ 1 501  20  1441 Jul 31 22:01 bin/sixsyn
> 	com.apple.FinderInfo	  32 
> 	com.apple.TextEncoding	  15 
> 
> Similarly, for files with a ‘+’ you can use the -e flag:

Well, yeah; but with 'xattr' you can find out what they are and get rid of the ones that are a problem (like, say, 'com.apple.quarantine').

> Incredible! One of the worst performances of my career and they never
> doubted it for a second.

Aw, you noticed.

Justin

--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's income
-----------
Question 43:
What if the hokey pokey
really *is* what it’s all about?
--
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.