Mac OS X 10.5.2 Update Brings Welcome Fixes 433
jetpack writes to make sure we're aware that Apple's OS X 10.5.2 update is available and that it contains plenty of improvements and fixes that users have been asking for. Macworld enumerates some of the big ones, saying that the update "shows Apple listens to users" (sometimes). A couple of the new features simply restore Tiger (10.4) capabilities that Leopard (10.5) had inexplicably withdrawn. You can now shut off the much-maligned transparency of the menu bar, and organize your Dock stacks hierarchically and display them as folders. And Apple has provided welcome access to common Time Machine functions in the menu bar.
AEBS backups (Score:5, Interesting)
Without reading the reversion list (Score:2, Interesting)
right direction (Score:3, Interesting)
Re:Does it bring back the "Windows Shade"? (Score:4, Interesting)
Another thing that I am only getting used to now is the whole Mac philosophy of windows not being full screen most of the time. It really does work if you give it a chance, but it is very alien to how I was used to working. So the "zoom" button, which most Windows users expect to be "maximize" doesn't work like you're used to. The point I'm trying to make here is that Apple aren't too lazy to implement all these windows-like behaviours, they really believe that their way of doing things is better. I don't really care one way or another, but I think many of the Mac ideas are pretty solid. I can tell you that I don't miss cut and paste on files at all.
Leopard Delays (Score:2, Interesting)
But the revised release date for Leopard was October 26th, 119 days after the day the iPhone would ship and those "borrowed" developers could return to work on 10.5. Four months put back into the timeline, not two. And in actuality the postponement gave Apple over six more months of Leopard development time, counted from the announcement on April 12th to the revised ship date on October 26th.
Apple had only borrowed a few key people, remember? Presumably the rest weren't just sitting around waiting for the others to get back to work.
Even with the extra time, Apple didn't have enough time to fix all of the problems. So as the October release date loomed, Apple rushed one more final candidate past developers, patched and polished a few last-minute issues, determined that it was "good enough", and shipped OS X 10.5 Leopard to the public.
So short was the time frame that few outside of Apple saw the gold master. Even major software development firms like Adobe received their final copies at nearly the same time as everyone else.
Is that the profile of a company that isn't rushing a product to market? Nope, 10.5.2 is what Leopard should have been [isights.org].
Re:Bah (Score:3, Interesting)
You can get a standard VNC client to connect to the built-in VNC server that ships with OSX. It takes some very specific settings, but it can be done. I've done it using TightVNC and UltraVNC on Windows before I finally switched to a Mac on the client side. If you Google around a bit, you should be able to find them.
Oh wait, the X Serve doesn't play nice with a standard KVM. I have an extra mouse and keyboard setting in my rack just for the X Serve.
Are you sure your KVM is standard? I have a 16-Port KVM complete with terminal, keyboard, and trackpad that works fine with the 6 XServes in the rack as well as with the FreeBSD, Linux, and Windows boxes in the rack.
Once you manage to get in the damn thing, if you have any sort of complicated setup at all, you simply CAN'T DO it using the server admin tool. I've usually had to bust into the config files just like any other Unix system. Take a look at the SQL section of the Server Admin tool, its a fucking joke. Also, even if you do start to do some things by hand, shit still doesn't work right.
That's what really sucks about OS X Server. Unless you have really basic needs that Apple envisioned, the GUI tools are useless. On top of that, you can't really customize anything that Apple has provided with the server. I tried compiling a custom PHP5 and installing the module on the stock Apache server only to have it crash Apache. I called Apple Support, and while they said it is technically possible to do what I was trying, they wouldn't provide any support for it. I ended up just compiling my own copy of Apache and PHP5 and saying to hell with the GUI tool.
On the other hand, OS X Server is awesome for managing a network of Macs. That's all about I can really recommend it for.
Re:AEBS backups (Score:4, Interesting)
Re:Send window to back? please? (Score:3, Interesting)
Re:Fonts fixed yet? (Score:3, Interesting)
Re:AEBS backups (Score:5, Interesting)
Every New Major version of OS X comes with a bunch glitches which they slowly but shirley fix in time. It happened in 10.1, 10.2, 10.3, 10.4 and 10.5 there are new features that pop in that people don't quite like that get adjusted, there is some odd combination that doesn't seem to work just right. and by 10.x.4 or so. things run so smoothly that you begin to forget the pain you once had, and By the time of the next version you are on 10,.x.10 or so. Where everything is rock solid. Then you get a New version 10.x+1 and it is full of these little glitches again, normally annoying but rarely a huge show stopper.
You are under the impression that Any Software Company with deep pockets can produce a bug free system, which is wrong. I could write a complex program and debug it and check it for a huge amount of time much longer then miss a simple bug. For example I was making a type ahead dropdown box in HTML/Javascript for an intranet app. I have tested and tested it it was perfect. Then when it went to testing it came right back saying the drop down box disappeared when ever someone scrolled down. What happened when I was testing it I always used the mouse scroll wheel to scroll down the list while other people just clicked the scroll bar to drag it down and caused a lost focus on my control, causing the menu box to go away. The fix was easy but the issue was I never though of testing it that way because I do things a particular way consistently. So does Apple, and the Beta Testers... So they could have worked out all the issues they have found then on Day one of the release someone just did that one thing they never expected.