Verizon Wireless
Troubleshooting Security Update 2003-07-14: Kernel panics, inability to mount disk images
The majority of readers are reporting no problems with Apple's latest security update (2003-07-14), intended to eliminate one of the security flaws in the Mac OS X Screen Effects component. We have also experienced no issues in-house after applying the update on a varied bunch of systems.
Some readers, however, received kernel panics at startup - as seems to have become the norm, at least for a small portion of those applying Apple-issued maintenance release - and report a broad array of miscellaneous issues, including an inability to mount disk images.
Remember, as with any releases obtained through Apple's Software Update, it is wise to repair permissions using Apple's Disk Utility immediately after installation. If you are still experiencing problems, try the time-test workaround of re-installing the Mac OS X 10.2.6 combo updater.
Feedback on the new security update? Late-breakers@macfixit.com.
Resources
(thus far). However, I've had it with all this "repair permissions"
nonsense. It's not that I expect computers to be maintenance free, but
this task of repairing file permissions has become more onerous and
frequent than rebuilding the desktop (under Mac OS 9) ever was.
What I don't understand is why it's necessary in the first place. I can
appreciate that certain install programs may need to change the
permissions on some files, but why can they not then change them back
and clean up after themselves? Frankly, I see no excuse for this --
particularly not when it often gives rise to bad behavior and failures
down the road. At the very least, a security patch from Apple -- of all
things -- should be installable without screwing up the file permissions.
And imagine the system administrator for a large network of Macs --
and having to run a permissions repair for each client on the network
after every software update. It's absurd.
If one is going to accept the responsibility of being an Administrator,
one must be disciplined about the process. What I had to come to terms
with was a tendency to install on a whim. I have learned to save up and
install apps on a weekly basis instead of a daily or even moment to
moment basis. After installing a number of updates, I then run Cocktail
to repair permissions and restart. -- Once a month I run bootCD with
Drive 10 and do all the tests, rebuild the Directory and then Optimize
the hard disks. My iMac 400Mhz SEDV (80G internal HD and
LaCie120HD) with 10.2.6 OS runs very quick and smooth.
---
BamaRose
Your point is well taken and I myself make it a practice to queue up
software updates and in fact to "field test" them first before populating
them throughout the network over which I preside. Unfortunately, this
doesn't address my original point in the least. Merely because an end
user CAN perform certain maintenance procudures does not mean he
should have to do so.
As I have said, at least until we reach the StarTrek age of technology, all
computers will require maintenance -- there is no escaping it. At the
same time, however, at least some maintenance is preventable with a
little foresight and design on the FRONT end -- by developers.
And I still have heard no good justification for installer/config programs
not to clean up after themselves. Surely you do not oppose this, (that
install programs would restore any file permissions they muck with), do
you?
Also, remember that a significant percentage of the Mac installed base
consists of consumers. It's not reasonable to expect them to be savvy to
all diagnostic and repair procedures. But at the end of the day, it comes
down to this: I see no good reason for software installers not to restore
at least those file permissions which they change. Do you?
Well said. I agree with you 100%!
---
Don't just do something, stand there!
It's not necessary at all. If it is, something is seriously bugged.
When you enter your admin password, you effectively give the installer
program root. As root, it can do anything, and has absolutely no reason
to require changing privs around, and doing so is a serious bug.
If it sets the wrong privs for files, it's bugged too.
Software Update rejected my trying to install this update saying that 343 MB of Hard Disk space was required to install this 1.7 MB update.
Something is seriously wrong here!!
Apple's Installer has always had a problem with wildly inflated
"estimates" of required install space.
You could try installing the security update with Pacifist.
on my G4 Powerbook 1GHz, 15" as p. ex. a VST 20GB USB/FireWire HD.
Nether CompactFlash Cards over a LEXAR jumpShot cable. Indeed, not
very funny! Any idea to fix this with an other software? Thanks
Hans J. Ruppert
- by April 6, 2004 5:21 AM PDT
- I seem to be getting kernel panics after receving updates.
- Like this Reply to this comment
-
(9 Comments)However, I also am getting them after repairing my disk with Disk
Utillity and then doing Repair Disk Permisisons. In one instance, I
ran Disk Utility, Drive 10 and TechTool Delux, then Repair Disk
Permisisons and I'm still getting the kernel panics.
Any suggestions?
Here is what I am running: Dual 1.25 Ghz Power Mac G4, 768 MB,
Mac OS X 10.2.8, cable modem, HP Laser Jet 1300
I'd appreciate any help.
Jim Murphy