Mta-interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com
On Jan 28, 2008, at 15:42:58, Dan Shoop 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.
Had you ordered Mac OS X Server software with your machine you
would most likely have not had this problem.
However optimistic this thought pattern might be, according to apple
the only solution that will resolve this bug with the newer
processors is OSXS 10.5.2 because it requires a kernel fix to get the
correct fsb base and it hasn't been released yet.
Subsequently there are two plausible solutions that I have tested and
both yield a working solution but one is not recommended and that is
to install the seed update, the other is to use pacifist and install
the client kernel and related files but this has issues with AFP so
if you're using it then this solution isn't recommended.
-dhan
----------------------------------------------------------------------
--
Dan Shoop
Computer Scientist
iWiring / U.S. Technical Services
For immediate response for urgent matters please speak to the Duty
Officer
at the USTS Tactical Operations Center (above) who can reach me by
radio.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40macftphttp.serverbox.org
This email sent to email@hidden
_______________________________________________
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
