Martin Costabel wrote:
After playing with this some more, I found that I was *not* able to transfer these dangerous permissions from the binary installer's pax file to the actual "/" directory when I used the binary installer as intended, i.e. by double-clicking on the "Fink 0.4.1 Installer.pkg" icon.Another clue might be the extract from the listing of the installer's pax filedrwx------ 3 2011 staff 0 Sep 22 22:57 .
The only way to get the bad permissions onto my disk was to do something low-level such as (as root)
gunzip < /Volumes/Fink-0.4.1-installer/Fink\ 0.4.1\ Installer.pkg/Contents/Resources/Fink\ 0.4.1\ Installer.pax.gz | pax -r -p 'e'
June Van Dyke wrote:
> Yep, we did have *major* permissions issues. For example, all 3 symlinks
> (which did exist) were u=rwx g=(nothing) o=(nothing). We're going to
> reinstall OS X, it's so messed up.
June, the permissions on symlinks reflect those of the parent directory, "/" in this case, not the permissions of the target directory. So the only thing that happened was the change in ownership and permissions of "/" (which can be repaired by "chmod 1775 /"; "chown root.admin /"), plus probably the wrong ownership of the whole /sw/ hierarchy.
> How the heck could this happen?
The jury is still out on this question.
Maybe those people who had the problem used some non-standard way of installing, like a program such as Pacifist, or an old version of Installer.app (there were several Software Updates that updated Installer.app), or some hand-crafted installing procedure?
--
Martin
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
