yesthattom: (Default)
[personal profile] yesthattom
http://www.info.apple.com/kbnum/n303411

Dear Apple, here are some comments I have:

"Prevents a potential issue in which Mac OS X might stop responding when trying to log in as a FileVault-protected user if the protected Home image file has been damaged or moved" -- Thanks. This is probably fixing the problem that crashed my computer and corrupted my NetInfo database to the point where I had to do a full reinstall. 2 weeks too late, bastards.

"If you are bound to a directory system which enforces password expiration, ... your keychain password will automatically be updated as well." -- So I paid $6,000 to your Enterprise group to have OpenDirectory set up and it never got completed because of this bug. Your engineer installed a third-party freeware app that eased the problem but became a usability nightmare. "Will Apple support this utility?" No. "Will Apple include this utility in the next release of OS X?" No. "Will Apple fix the fundamental problem so a utility isn't required?" We're not allowed to say. "Enterprise Support" at all other companies means that once a bug is scheduled to be fixed in a particular release they'll tell you. Instead, Apple continues their policy that "Enterprise Support means you pay us a lot of money and we do nothing."

"Resolves potential issues that could occur when using automatic proxy configuration (PAC) files." -- I hope this is the problem that I run into about every other day.

"Disk Utility's repair permissions feature will no longer report "We are using special permissions for..." messages." -- And did you hunt down and kill the developer that created this message? What does the code look like, /* Spew random error messages that almost make sense but only if computers used tri-nary instead of binary. */"

"Resolves an issue that could cause Help Viewer to sometimes display a blank window." -- I thought it was just emulating the "blank look" stare that I get from your phone support people anytime I ask a question that can't be solved by rebooting.

"Terminal windows will no longer fail to open when using the /bin/zsh shell." -- I thought you were just discouraging people with bad taste.

"Addresses an issue for Microsoft Word 2004 in which Word would display a "Word cannot complete the operation because too many files are open" alert message when autosaving a document to a network-based home directory." -- I used to have a user that got this error constantly. I quit that company 5 months ago and the user was laid off last week. A dollar short and a day late.

And now the grand finale!!!

"Makes Mac OS X aware of United States Daylight Savings Time (DST) changes enacted by the Energy Policy Act of 2005." Oh your motherfuckers rolled out a fix for this the WEEK AFTER the first time this was needed! Fucking brilliant!

Oh sweet jesus I'm laughing so hard it hurts! Make it stop! Make it stop!

Date: 2006-04-04 01:42 pm (UTC)
From: [identity profile] niallm.livejournal.com
Apple is bad at Enterprise support because The Steve can't get excited about it, and no-one is sufficiently pig-headed or powerful to wrest that amount of control away from him to do it properly.

Which is a shame, really.

Date: 2006-04-04 03:54 pm (UTC)
From: [identity profile] kimuchi.livejournal.com
I also get the impression that the bug notification Tom expected is beyond Apple's organizational wherewithal. They seem like far too much of a crazy anarchy internally from what I hear, especially around bug escalations.

Date: 2006-04-04 02:15 pm (UTC)
ckd: small blue foam shark (Default)
From: [personal profile] ckd
The DST changes are for next year. The changes this year in Indiana? Those were caused by local idiots, not Federal idiots.

Date: 2006-04-04 03:07 pm (UTC)
From: [identity profile] nooks.livejournal.com

And in fact, apple appears to have beaten Debian to the punch on this one:

$ zdump -v -c 2005,2008 US/Eastern
US/Eastern  Fri Dec 13 20:45:52 1901 UTC = Fri Dec 13 15:45:52 1901 EST isdst=0 gmtoff=-18000
US/Eastern  Sat Dec 14 20:45:52 1901 UTC = Sat Dec 14 15:45:52 1901 EST isdst=0 gmtoff=-18000
US/Eastern  Sun Apr  3 06:59:59 2005 UTC = Sun Apr  3 01:59:59 2005 EST isdst=0 gmtoff=-18000
US/Eastern  Sun Apr  3 07:00:00 2005 UTC = Sun Apr  3 03:00:00 2005 EDT isdst=1 gmtoff=-14400
US/Eastern  Sun Oct 30 05:59:59 2005 UTC = Sun Oct 30 01:59:59 2005 EDT isdst=1 gmtoff=-14400
US/Eastern  Sun Oct 30 06:00:00 2005 UTC = Sun Oct 30 01:00:00 2005 EST isdst=0 gmtoff=-18000
US/Eastern  Sun Apr  2 06:59:59 2006 UTC = Sun Apr  2 01:59:59 2006 EST isdst=0 gmtoff=-18000
US/Eastern  Sun Apr  2 07:00:00 2006 UTC = Sun Apr  2 03:00:00 2006 EDT isdst=1 gmtoff=-14400
US/Eastern  Sun Oct 29 05:59:59 2006 UTC = Sun Oct 29 01:59:59 2006 EDT isdst=1 gmtoff=-14400
US/Eastern  Sun Oct 29 06:00:00 2006 UTC = Sun Oct 29 01:00:00 2006 EST isdst=0 gmtoff=-18000
US/Eastern  Sun Apr  1 06:59:59 2007 UTC = Sun Apr  1 01:59:59 2007 EST isdst=0 gmtoff=-18000
US/Eastern  Sun Apr  1 07:00:00 2007 UTC = Sun Apr  1 03:00:00 2007 EDT isdst=1 gmtoff=-14400
US/Eastern  Sun Oct 28 05:59:59 2007 UTC = Sun Oct 28 01:59:59 2007 EDT isdst=1 gmtoff=-14400
US/Eastern  Sun Oct 28 06:00:00 2007 UTC = Sun Oct 28 01:00:00 2007 EST isdst=0 gmtoff=-18000
US/Eastern  Mon Jan 18 03:14:07 2038 UTC = Sun Jan 17 22:14:07 2038 EST isdst=0 gmtoff=-18000
US/Eastern  Tue Jan 19 03:14:07 2038 UTC = Mon Jan 18 22:14:07 2038 EST isdst=0 gmtoff=-18000

I don't understand the last two lines of output, but the rest of it is pretty darn clear. Oh, 2038. I see.

Date: 2006-04-04 03:07 pm (UTC)

Date: 2006-04-04 03:08 pm (UTC)
From: [identity profile] penk.livejournal.com
/me puts on the *NOT AN APPLE FAN* hat.

for just these reasons.

Apple is great as a hobbyist / fun platform. But they suck when trying to do business.

Golinux :)

Date: 2006-04-04 03:51 pm (UTC)
From: [identity profile] kimuchi.livejournal.com
I don't think I agree. Then again, the last place I worked with Linux on the desktop, IT neglected to install it with a working mouse config. Not really their fault -- I at least expect an OS considered suitable for deployment in a corporate desktop environment to support commonly used name-brand mice out of the box. I also ran Linux on a laptop for years, which made me delight in the out of the box power management and no-tweaking PCMCIA support in OS X.

Date: 2006-04-04 06:52 pm (UTC)
From: [identity profile] penk.livejournal.com
Without getting into platform wars, I think this is a failure in your IT department. If they had installed Windows without a working mouse, you'd have the same problem.

I use linux desktops for 100% of my day to day operation, laptops, development, browsing, graphics work, communicaiton, email, everything. The only reason not to use it is if there's an application you need that is not available under linux (which, alas, includes a lot fo the 'munst have' systems, like Quickbooks, etc).

FWIW, my laptop installs (all 3-4 of them) have supported power management and PCMCIA support out of the box.

Date: 2006-04-04 06:58 pm (UTC)
From: [identity profile] yesthattom.livejournal.com
I've never seen a Linux laptop do power management as well as a Mac OS X box.

(and having all the mouse drivers work on the first try is an IT issue... technically... but the fact that device support is so good on OS X has a lot of benefits. I mean, the darn mouse works in [the equiv of] BIOS mode!)

Date: 2006-04-05 08:20 am (UTC)
From: [identity profile] kimuchi.livejournal.com
It *is* a failure of the IT department, but as I said it was a major name-brand mouse that Windows and MacOS both would've supported out of the box. I don't think it's unreasonable to expect the same from anything else being promoted as an enterprise-appropriate desktop...along with tools for fixing the problem that work properly (for whatever reason the config tool (kvmconfig? It's been a while) in this version of RedHat didn't write the mouse config file properly, so it had to be written by hand) and have current, correct documentation.

Don't get me wrong, I enjoy working with linux as a server software development platform. I just think it's unrealistic to claim it's a well-developed choice for the desktop.

Date: 2006-04-04 04:08 pm (UTC)
From: [identity profile] gwenix.livejournal.com
OK, beyond the Shell Wars...

I'm really glad they fixed the zsh issue. I wondered why half the time I tried opening a window, it'd just... fail.

Date: 2006-04-04 06:09 pm (UTC)
From: [identity profile] airshipjones.livejournal.com
Geez. It is no wonder Windoze Server sales were up over 20% last year.

Date: 2006-04-04 07:23 pm (UTC)
From: [identity profile] dr-memory.livejournal.com
I love Mac's unreservedly as personal and home computers, and even think they're probably a good choice for small companies... but yeah, Apple's "enterprise" support is a sick joke.

I can't blame them for being gunshy about trying to compete with Microsoft and Novell on that turf, but that doesn't make it any more fun to deal with. Frankly, I wish they'd just license whatever's necessary from Microsoft to make OSX a full ADS client, and just be done with it.

December 2015

S M T W T F S
  12345
6789 101112
13141516171819
202122 23242526
2728293031  

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 26th, 2025 09:57 am
Powered by Dreamwidth Studios