On 5/24/10 4:16 PM, john gale wrote: > > On May 23, 2010, at 4:29 AM, Hanspeter Niederstrasser wrote: > >> On 05/21/2010 7:59 PM, john gale wrote: >>> % /sw/bootstrap/bin/dpkg -L base-files >>> /._. >> >> ALL the files in the package have a dot_underscore companion. I didn't >> see that at first and thought that maybe it was some preexisting >> condition on your HD, but it seems to be an issue with the bootstrap >> process and deb creation instead. Do you have 2 hard drives, or are >> using File Vault, or anything that could be creating a volume that the >> system is thinking is not HFS+? Or have you installed a non-system >> utility like tar, fileutils, or similar? >> >> Out of curiosity, what is the size of /._. and what does 'file /._.' say? > > -rwxr-xr-x+ 1 root admin 491 May 21 16:57:20 2010 ._. > > % cat ._. > Mac OS X 2??ATTR?U??S?Scom.apple.acl.text!#acl 1 > user:72247D1E-7867-4783-B97F-5A533167BFF9:john:505:allow,inherited,file_inherit,directory_inherit:read,write,execute,append,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity,writesecurity,chown > user:FFFFEEEE-DDDD-CCCC-BBBB-AAAA00000059:_spotlight:89:allow,inherited,file_inherit,directory_inherit:read,execute > > I do have several drives, but no filevault, nor anything else that should be > messing with the FS statistics. > > It looks like the contents of the /._. file is a text representation of the > ACL that is also on /._. and to some degree on / as well. > > Is there some part of the installation process that is attempting to write > ACLs to the various folders? It seems to be not writing the ACLs correctly, > and instead storing them all in ._ files.
Fink doesn't use ACLs as far as I'm aware. Some packages use specific users, but don't do ACL stuff. The fact that _every_ file in the .deb has a /._ partner highly suggests something is going on with the FS and how extended attributes are being handled. Have you checked the system with Disk Utility lately to see if that reports anything? Look back through your bootstrap log and see where the package base-files is actually being created. Do you see any instances of /._ during the process, or is the conflict between the fink .deb and base_files (from your first post) the first time a /._ file shows up in the log? If you manually create a new file via Terminal (echo "hello" > ~/test.txt) or create a tarball from an existing directory (tar vcf ~/test.tar ~/Sites), do they end up with a corresponding /._ file (or inside the tar file (tar tf ~/test.tar)? Hanspeter ------------------------------------------------------------------------------ _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
