Slashdot Mirror
Panther Problem Roundup
An anonymous reader writes "SecureMac has posted an advisory on Mac OS X 10.3 Panther's screen lock. Apparently, to a limited degree, keys being pressed before the authentication window pops-up are sent to the currently logged-in user's environment. Note: Security Update 2003-10-28 version 1.0, which was released shortly after the advisory's release, does not fix this issue, but rather a hole in QuickTime for Java." Another anonymous reader writes "A problem with Panther has been found with external FireWire drives, that causes FireWire disk partitions in Panther above 137GB to be shown as corrupt after a reboot, in most cases being entirely unaccessible and unusable." And as a public service to all you mail rebels, I found out -- for me, anyway -- how to send email under Eudora without crashing.
The biggest problem for me is that uControl apparently doesn't work, so I won't be able to swap control and caps-lock if I upgrade. Since my hands are hard-wired to find the control key to the left of the 'a' key, this is a showstopper for me.
Does anybody know of any other way to swap control and capslock on an Apple Powerbook (ti, 866MHz)? Xmodmap apparently doesn't work either. This copy of panther is burning a hole in my pocket..
A problem with Panther has been found with external FireWire drives, that causes FireWire disk partitions in Panther above 137GB to be shown as corrupt after a reboot, in most cases being entirely unaccessible and unusable.
I've been using a 160GB drive over Firewire since Jaguar. I did an "archive and install" of panther, and the same drive still works great.
I did, however, turn the drive off while I was installing the OS. I wonder if that has anything to do with it? Or perhaps its a particular Firewire chip/controller causing the problem?
Perl - $Just @when->$you ${thought} s/yn/tax/ &couldn\'t %get $worse;
I had the same problem with one of the betas. I started with Filevault on, thinking that I would rather have it incrementally encrypt files as I brought them into my home directory instead of waiting for it to do them all at once. It worked great for a few weeks, seemed a lot more stable then the previous build so I didn't upgrade to the next released build. Then all of a sudden I turned my computer on, tried to log in and it sat for 10 minutes doing something. Finally I got impatient, figured I had a journaling file system and did a hard reset. Ooops. When the PowerBook came back up my username and password worked but my home directory was empty.
That wasn't the result I was hoping for.
Filevault is one of the most touted features. I'm sure it works great, never tried to crack it.
Maybe they shouldn't have implemented secure delete and FileVault all at the same time. They seem to work a little too well together.
Personally I do not consider it 'advanced' to have to wipe my drive once a year, but to each his own.
If Jesus wants me it knows where to find me.