Only because an issue of "machome" says in the march 2004 spring cleaning section "one folder you can emty: Macintosh HD>Library>Receipts" I did it to clear some disk space
Only because an issue of "machome" says in the march 2004 spring cleaning section "one folder you can emty: Macintosh HD>Library>Receipts" I did it to clear some disk space
Yep, the magazine fukked up real good on this one. Lots of people have this problem, and are not too happy about it. Make sure to write Mac Home a real nice thank-you letter.
I found out the problem: the package BaseSystem.pkg must be in the reciepts folder or the permissions repair won't work. I was able to copy the file right off the mac os 10.3 cd 1.
ahh screw it. . . I went a year with 10.1.5 without repairing permissions ill just wait for "Tiger whenn i'll do a clean install, after I get a new firewire HD.
I found out the problem: the package BaseSystem.pkg must be in the reciepts folder or the permissions repair won't work. I was able to copy the file right off the mac os 10.3 cd 1.
Anyway, same "thing" happend to me therefore the solution was booting up from original Xcd, repairing permissions from there and though...
Comments
Only because an issue of "machome" says in the march 2004 spring cleaning section "one folder you can emty: Macintosh HD>Library>Receipts" I did it to clear some disk space
Originally posted by Nano
Yes
Only because an issue of "machome" says in the march 2004 spring cleaning section "one folder you can emty: Macintosh HD>Library>Receipts" I did it to clear some disk space
Yep, the magazine fukked up real good on this one. Lots of people have this problem, and are not too happy about it. Make sure to write Mac Home a real nice thank-you letter.
Do you have a backup pre-clean that you can use?
Originally posted by Nano
I found out the problem: the package BaseSystem.pkg must be in the reciepts folder or the permissions repair won't work. I was able to copy the file right off the mac os 10.3 cd 1.
Anyway, same "thing" happend to me therefore the solution was booting up from original Xcd, repairing permissions from there and though...