Xtremehkr said:How come I never have any problems when I update my little G3 600Mhz?
Xtremehkr said:How come I never have any problems when I update my little G3 600Mhz?
Zaty said:That's because Panther will never run on a PB G5, they will come with Tiger pre-installed.
Abstract said:Yeah, software updates are cool, but Calculator?
heaven said:Just updated, no problems here so far!
Thx Apple!
![]()
neonart said:I'm always intrigued by the large amount of people with weird problems. I wonder if these are people who never repair permissions, have tons of mods and hacks, or install every demo and piece of freeware they can find? Then once an update comes along and shuffles things around they get these problems.
I never knew what that was all about.iMeowbot said:That's a feature, not a bug.
If we look at the file before running the permissions repair, we see:
The -rwxr-xr-x in octal is 0755.Code:$ ls -l /System/Library/Filesystems/cd9660.fs/cd9660.util -rwxr-xr-x 1 root wheel 20436 5 Nov 17:15 /System/Library/Filesystems/cd9660.fs/cd9660.util
Running the permissions repair, we are told:
Converting 33261 to octal, we get 0100755. That's really the same thing as 0755; the additional 1 in there is just a more verbose form showing us that this is a regular file (as opposed to, say, a fifo, device or symlink). [see S_IFREG in /usr/include/sys/stat.h]Code:We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
Performing the ls -l after running the permissions repair will confirm that the file's permissions have not changed.
In other words, Disk Utility is just making extra sure that cd9660.util has the correct permissions by forcing the issue rather than doing it conditionally.
iMeowbot said:That's a feature, not a bug.
...
Performing the ls -l after running the permissions repair will confirm that the file's permissions have not changed.
dmealiffe said:I'd love to try the update, but Software Update crashes approximately 75% through the progress bar. It doesn't even show the update in the list before it dies!
Anyone have any ideas? I just recently upgraded my processor to a 1.4 GHz OWC module, but that shouldn't cause any trouble, should it?![]()
It's really there for installation. The package has the permissions marked as forced, to help prevent a regression, and its appearance in Disk Utility that way is a side effect, just a message noting that it's being forced. Given all the different patch levels it's possible to have with a Panther system, it makes sense to stomp a bug from more than one angle. If the patched binary somehow fails to get installed, the package info offers a second chance to render it harmless. Makes sense to me...Rower_CPU said:So the "feature" doesn't change anything...everytime? Doesn't sound like a feature to me.
iMeowbot said:It's really there for installation. The package has the permissions marked as forced, to help prevent a regression, and its appearance in Disk Utility that way is a side effect, just a message noting that it's being forced. Given all the different patch levels it's possible to have with a Panther system, it makes sense to stomp a bug from more than one angle. If the patched binary somehow fails to get installed, the package info offers a second chance to render it harmless. Makes sense to me...
Rower_CPU said:Dunno - to me the brute force approach is poor programming. If permissions repair actually works correctly, it should be able to detect that the permissions are correct and not "fix" it every time. Guess I just prefer the conditional method.
TigerKR said:Hardware Config:
MDD DP 1.25 GHz G4 Tower
10.3.6 and all updates, permissions repaired
no third party audio hardware
Description:
After updating, audio volume was increased, and quality was decreased.
Hypothesis:
I looked on the Apple Discussions and someone with the same problem said that they fixed this problem by zapping their PRAM.
Solution:
Zapping the PRAM does fix the audio volume/quality problem for me.
neonart said:I'm always intrigued by the large amount of people with weird problems. I wonder if these are people who never repair permissions, have tons of mods and hacks, or install every demo and piece of freeware they can find? Then once an update comes along and shuffles things around they get these problems.
Nikita:/Users/foouser root# cd temp
Nikita:/Users/foouser/temp root# ls -al
total 48
d--------- 4 foouser foouser 136 6 Nov 10:45 .
drwxr-xr-x 77 foouser foouser 2618 6 Nov 10:45 ..
---------- 1 foouser foouser 20480 6 Nov 10:45 Copy User Account Request.doc
---------- 1 foouser foouser 2571 6 Nov 10:45 xinitrc.term
Nikita:/Users/foouser/temp root# cat xinitrc.term
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>WindowSettings</key>
<array>
<dict>
<key>AutoFocus</key>
<string>YES</string>
... <--- Clipping out a bunch of stuff that's unnecessary to make my point
<key>WindowCloseAction</key>
<string>1</string>
</dict>
</array>
</dict>
</plist>
Nikita:/Users/foouser/temp root#