Post a Comment
microsoft releases plenty of bugfixes too but they don't aggregate them into service packs as often as apple releases point releases.
however, I do tend to agree with previous posters that tiger was released a little too soon. I didn't upgrade to tiger until 10.4.2 for this reason and i've had no problems except samba/debian linux-connectivity (I can connect to win xp smb mounts just fine)
Let's be honest here. There are always minor improvements you can make to any software product. Wether it is a bugfix or a new feature, there is always something. Personally, I wouldn't have wanted to wait another month for getting Tiger. 10.4.0 and 10.4.1 gave me little problems, and added extra "value" to my workflow over Panther. I don't see why they should have waited any longer before they introduced Tiger.
You're lucky. I'll probably make an erase and install and I think everything will work then (I have always made archive and install). As I said, I'm not alone, and in fact we're quite a number to have had problems with MySQL/Tiger.
Is it forbidden to have problems, even rares ? Or to say so ? Or is the fact that I have a problem offensive to someone ? Because I can't see why I have been moded down.
Everytime I go to a new version of Mac OS X I save my data to a hard drive then do an Erase and Install so it's a fresh installation. Idk if there are that many problems as a result of upgrading on Mac OS X vs erasing and install but so far using the latest MySQL on a new copy of Mac OS X 10.4 Tiger has worked well in the tasks I use it for.
FULL DISCLOSURE: I am a Mac Guy.
I honestly hope Apple gets it right with this next patch of Tiger. Tiger is so buggy, it's not even funny.
I hate to hammer Apple like this in public, but they really deserve it. I cut Apple some slack after seeing the bugs in the original release because I figured they had some products which required Tiger or needed to launch it to meet Wall Street numbers. Now we know neither was true.
So Apple basically released a very buggy OS. .1 and .2, while fixing hundreds of bugs, did not go anywhere near far enough in terms of getting Tiger to a commercial quality OS.
I hope .3 fixes HUNDREDS and HUNDREDS of bugs--not the 50 or so that is being reported. Yes, Tiger needs that much work.
Look, I am a techie, so I know no software is bug free. Of course. But I also know when software is below the acceptable threshold, and while Tiger does not corrupt data or anything of that ilk, the number of bugs--even in .2--is still unacceptable.
I hate talking about Apple this way. I really do. But they should of known better.
Tiger has been very solid for me. Same is true of my deployment of Tiger in the office. I wouldn't say there are hundreds and hundreds of immediately apparent bugs at all. Furthermore there's been no serious discussion that I'm aware of that Tiger is so hideously buggy as you describe.
Everything is stable here too; the only people whining, from what I have seen, are those who are either using buggy third party drivers, buggy third party hackware programmes so they can "tweak" MacOS X, or running third party, unneed tools like "Norton System Works" which cause more harm to stability than what they set out to fix.
@kawai
You are a bit harsh in your statement. Some people experienced real problems during migration. Here you have my story. Learn something.
When we migrated our whole Mac line from Panther to Tiger, everything went okay. Then we went on to 10.4.1 and again, everything smooth except one Powerbook: mine. That's a 17" 1Ghz machine with 1Gb offical Apple memory and no third party unneeded tools, hackware stuff or other small buggy programs. I experienced strange things from: slow processing, unexpected reboots, kernel panics and in the end a good old crash and gone was my OS. I reinstalled a couple of times including clean install, upgrading from clean Panther to Tiger and from clean Jaguar to Tiger. Was no solution, problem remained the same.
Sure I 'whined' about it, despite being a hardcore Apple fan. You might even call me a fanboy, but in the end it's all about me being able to do my work. I couldn't do my job, because of this update and thus I complained. And don't start with: You don't have to upgrade. Indeed I don't have to upgrade, but here we have a supplier which simply released something that f*cked up my super stable workhorse. Simple is that, no matter how much I love their products.
I called Apple support (which was pretty decent btw) and posted my problem on multiple boards. The quality of the feedback I got, showed a more open mind than that you put down here. The Apple community is really good.
In the end it appeared to be corrupt system memory (despite being Apple memory, bought at the Apple store!!). The problem was gone when updating to 10.4.2 and my system is as stable as it was before. I seems a bit faster too.
Given the time I had to pour in to make that powerbook run again (and purchasing a spare 12" to buy time), I would say it was a mighty expensive update for me. On the other hand: all other systems here got updated without a glitch, so it appeared to be a one out of 20-something probleem.
But the last thing I - and the community - needs, are people like you. People saying that only 'whiners' have problems. Get real ... in 1997 Windows fanboys said the same about people complaining about the fawlty Windows how-to-deal-with-security-concept ... look where it got the platform, speaking from a technical point of view.
I experienced a kernel panic in 10.4.2 while unplugging the power adapter (system was switching to battery). This was definitely the most gorgeous system crash I've ever seen (transluent dialog indicating that it was necessary to restart or powerdown the system --in multiple languages even!) I had not seen an OS X kernel panic since the 10.0.x days but the problem does not seem to be reproducable.
While Tiger was released too soon, the versioning isn't a bad idea. I mean it may sound goofy at first that you're running 10.4.14, but at least you easilty know which (mini) service pack has been applied.
Although the only way to keep sanity is to include ALL previous updates with each new service pack and downloading a 30+ meg service pack every 4 weeks is asking a lot.
Perhaps this isn't better than the way Apple use to version their updates. (ala the way MS is and has been doing it)



