On Jan 28, 2008 3:42 PM, Dan Shoop <email@hidden> wrote:
> On Jan 27, 2008, at 2:55 PM, Michael Steinfeld wrote:
> > On Jan 25, 2008 5:03 PM, Steve Maser <email@hidden> wrote:
> >>> Yup, Gotta love how apple has not addressed this issue. I've had my
> >>> Mac Pro for almost 2 weeks now. So basically we are all SOL. That's
> >>> the price you pay for being an early adapter to Apple HW/SW
> >>> upgrades.
> >>> Makes me think now about my iPhone dilemma how I paid a premium to
> >>> have it right away (Before they lowered the price). That's twice
> >>> this
> >>> year that impulse for Apple products has gotten the better of me.
> >>> Lesson learned. I won't make this mistake a third time.
> >>> -Mike
> >> 10.5.2 is likely to be out "any day now".
> >> We haven't tested the server seed build on the MacPro, but we might
> >> do that if it's not officially released on Monday.
> >> But, it's not unusual for Apple to have new OS builds for new
> >> hardware. Been like that for years and years...
> > Yes they have. But that doesn't mean that your brand new $1000.00
> > Server software should need an extra 3 weeks before it is compatible.
> > That is ridiculous. However, aside from my opinion about that, what
> > amazes me even more is that Apple didn't even catch this MAJOR bug
> > going out the door. Maybe Apple is snoozing while watching their stock
> > price pass $200.00. Oh look, it's around $130.00 again!! Maybe they'll
> > start paying better attention to what the <$#*&> is going on.
> > This is not a minor bug, the machine is completely useless with
> > Leopard Server right now. SO shoudn't there be a patch for this bug
> > already? After all it is fixed with the kernel that ships with the new
> > mac pro's.
> > I absolutely love my mac pro. For years I have dreamed of an
> > aesthetically pleasing unix desktop.. but I am learning more and more
> > to going back to FreeBSD or Linux everyday.
> Let's be clear. You only got bitten by this b/c you didn't order the
> correct software with your new hardware. The software you ordered with
> it worked just fine. But you wanted to install older software on it
> and then started whining.
Let *us* be clear Dan, You are not a cowboy, but you need to go
outside and ride a horse. It will be good for you.
> Had you ordered Mac OS X Server software with your machine you would
> most likely have not had this problem.
Right, because I purchased the latest available Leopard Server 2 weeks
previous, I was completely an idiot to think that it wouldn't work in
a new Apple machine. Sorry, but not all of us become troglodytes and
live and breath every thing Apple does. Common sense tells me.. you
are an Apple *Kiss-Ass* however smart you may be.
Get over yourself. It's a Horrible BUG. I'm not even sure Microsoft
would have let this out the door. It would be one thing if 10.5.2 came
out a few days after, but a month? Why the hell would I pay for OSX
Server again, just because I got a new machine two weeks before a new
machine I bought was not even out yet? The issue is that apple does
not release an update for those that have to suffer this bug. NOTE:
These are APPLE CORPORATE CLIENTS.. something apple has not given a
shit about for a long time.
Sorry Dan Shoop, but just as you are wrong about the kernel updates,
you are wrong in this regard as well.
So since you felt the need to insult me, as you do to everyone that
isn't kissing you cheeks the same way you kiss apple's. Do I need to
say more? You can carry on now, camper.
> Dan Shoop
> Computer Scientist
> iWiring / U.S. Technical Services
> AOL IM .................... iWiring
> Nextel .................... 1-714-363-1174
> Operations TOC (24/7) ..... 1-866-901-USTS
> USTS Offices .............. 1-714-374-6300
> For immediate response for urgent matters please speak to the Duty
> at the USTS Tactical Operations Center (above) who can reach me by
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden