Slashdot Mirror
Apple Secretly Maintaining x86 Port Of Mac OS X
Earlybird writes "According to this eWeek article, Apple has ported the whole of Mac OS X to the x86 architecture and is maintaining it in parallel with the PowerPC builds. Dubbed Marklar, the project is perceived as a fall-back plan, and, quoth the article, 'has apparently gained strategic relevance in recent months, as Apple's relationship with Motorola has grown strained and Apple looks to alternative chip makers.'" Believe what you will ...
They have ported all of Mac OS X to x86? Not just the kernel?
:)
Let's pool $100,000 (Blender-style) and bribe the guy who runs their internal CVS repositories. Anyone wanna throw in a few bucks for macosx-x86-0dayl33t.iso?
qslack.com
How long 'til we get to see some leaked photos of Apple-specific X86 hardwware?
Here I'm posting an article I wrote about the Mac OS X on the PC Platform long ago and that I tried getting publish on /.. Well, maybe now is a good time to post it after all
.Net Server Beta). Eventually (the truth hurts folks), Windows will be as fast and stable as Linux, and yes, they will copy the Mac look and get away with it just as they did with Windows. And they will have a market of several hundred million users who (like a herd) will simply follow Microsoft because simply they're not tech-savvy enough to realize that there are other choices. And developers will continue increasingly target the Windows platform because numbers speak: Do I sell for 4 million Linux machines, 5 million Mac machines, or 500 million Wintel machines?
As we all know, with Linux we have the best free (as in beer) operating system in the market. It's fast, it's stable, it's well-supported, it scales, and it has a GUI environment that although very acceptable to the Linux community, it really is not up to par to the elegance and simplicity of the Mac OS/X GUI (and god spare me some flames, even the Windows XP interface feels better than the "stock" KDE or GNOME shipped with Linux).
On the other hand, we have Mac OS/X, the most amazing GUI out today for any platform. It certainly makes our friend Bill G. jelaous. It also has an amazing rendering engine by sporting PDF under the hood. However, even though it has a great backbone in the form of an open BSD system, the truth is that it is doubtfull the apple folks will get the steam, hype, and generally market support that Linux is constantly getting lately in all media, corporations, and geeks alike. Add to that the fact that Mac OS/X runs only on the PowerPC platform (at least officially), and you get a lot of potential market away from Apple.
So how about this, why not have Apple port it's whole Mac OS/X upper layers to the x86 platform, publish some specs for Linux vendors to "plug under", and run it on top of such Linux-based (as opposed BSD-based) systems???
With this we'd get the great support Linux enjoys in the enterprise (even when I'm first to recognize that BSD is just as good technical-wise, but this is a market-driven world folks), it'd also get the support from the millions of geeks who own a x86 machine, it'd get the support of all the OEMs who would almost inmmediatelly start providing hardware/software products for the platform, and just as important it would get the support of the common user thanks to its simple, elegant, and fast GUI system.
As a matter of fact, I'm pretty sure soon after we could start converting all Wintel users to the new platform ("Mac OS/Linux"?), since a new hardware investment would not be needed. Just a software download and a much lower price than a Windows license (say, 50 bucks?).
I know, some will argue that "what makes Macs different is the tight integration of the OS with the hardware" and blah blah blah, but heck, should this that I propose take off, I'm sure that Apple will have enough leverage to publish standards making this integration much simpler and still remain open, while benefiting everyone.
Note that since the Mac OS layer would sit on top of a MacOS-compliant Linux distro, it means that teckies will NOT be forced to use the Mac OS GUI, since they could use their Linux distro as usual, minus the Mac stuff. They could even keep using their old KDE or GNOME GUIs.
So, how does Apple make money? selling the top layer (software services and GUI), and if they want even selling slick custom-built hardware boxes like they do today with the OS pre-installed.
Now, please stop all the flames about "sotfware should be free and I shouldn't have to pay to use the Mac OS/X layer on top of Linux" and all that. Software should be free, but people also have families to take care of, and Apple's effort should be rewarded by paying them. Case closed.
As for Linux, imagine all of a sudden a flood of trully useable applications being ported from the Mac (and even Wintel) world to the new "Mac OS/Linux". This would eliminate the barrier many have when trying to move from Wintel to Mac: "my apps don't work or I can't access my data".
Also imagine the simplicity of installing, deinstalling, and managing applications that Mac OS would bring (do not tell me how debian, RPMs, etc are great, they suck big time if you ever had to use them regularly; yes I have).
This, I think, it's what would really bring a true competitor to the Windows monopoly. I'm sure that *I* would switch inmediatelly.
And BTW, as an example let's take my own case: I do not use Linux regularly because it's just too darn hard to do anything (unless you _already_ knew how to do it). Sure once you get it working it's fine and dandy, but heck, sometimes to get it to work you have to get the sources, read the FAQs, HowTos, set some flags, find dependencies, get extra libraries, etc.
Likewise, I don't use Mac OS/X because I can't go out and afford to buy a whole new machine architecture. I already have my decent 1.2Ghz Celeron, it works fine, why should I switch and spend US$1,700 just to use a nice GUI?
However allow me to keep my machine, give me the stability and power of Linux, and the elegance and simplicity of the Mac, and you can count me in right away.
Now don't get me wrong, Linux is *awesome* for someone that knows how to use it, or has the time to learn it. I think's it's an amazing platform for Apache, mySQL, PHP, firewalling, routing, Java, Perl, etc, but it could be much more if it was easier to administer and use.
You gotta understand that the people in large corporations are afraid of getting into something they don't understand or think it's too complex, this is why Windows NT has gotten such a large market share; People very close to me admit it, they use WinNT even if they have to reboot it once every 2 weeks because it is *easy* to use. And folks, yes I agree that maybe "they're not qualified enough to have such a job", but the reality is that they are here to stay and always will be here to stay, and Microsoft is counting on them.
Add to all this the distressing fact that the Windows OS _is_ getting better all the time (ask a Win95/98/Me user how many times they rebooted WinXP lately, or check out the Windows
This is the time folks to trully all come together and trully create a second option to Wintel. Let's combine the best of what we have (a Linux foundation, X86 hardware, and Mac OS upper services and GUI layers), and trully create something we can be proud of a few years from now.
So what's the next step? Someone should send this article to Apple's Steve Jobs, and have Steve meet with the heads of the major Linux distros to define some specs that all would follow to support the Mac Layer. Rally some OEMs to make their products "Mac Linux"-ready (so that they could support the tight-integration features that makes Macs such a joy to use today), and rally the big software developer houses and let them know about this and get them excited, and let's all rally behind this effort and give them all the support the open source community is famous for. This could be the beginning of a trully beautiful relationship...
If they release on intel hardware it will be for a finite set of manufactures to a limited set of specs, so that they can continue to deliver true plug-and-play. Expect to pay more for intel based hardware that runs Mac OS X.
And don't be too disapointed if your current system is not supported.
-b
I hope this new marklar really works on marklar marklar. Marklar seems to be the marklar of the marklar, not just another markler off the old marklar. Marklar really does need to marklar another marklar maker in order to be marklar with the marklar. Marklar is just not marlar anymore, and this seems to be a good marklar to the marklar. A small marklar to marklar, really.
Moon Macrosystems. Sun's biggest competitor.
It is much more plausible that Apple is switching the 64-bit IBM Power4 CPU. IBM is presenting this new desktop version of the CPU at Microprocessor Forum on October 15th. The CPU has a mystery vector unit with 160+ instructions, just like AltiVec. There was a post to the gcc-patches mailing list proposing a patch to enable altivec support on the powerpc64 target, and this patch originated from Alan Modra at IBM's Linux Technology Center.
All evidence indicates that IBM will produce a desktop CPU with an AltiVec unit. Apple has hit the wall with Motorola, and are now selling overclocked G4 miracle CPUs just to stay in the game. I think Apple will switch to Power4.
This would have been when Windows 3.1 was the best Redmond had to offer, but I'm not sure the MacOS of that era would have been much better.
Geez, are you kidding? System 7 was FAR AND AWAY better than 3.1 ever was. I remember reading a compariason of System 7 to Win 3.1 in a MacUser issue from back in '90. System 7 formed the basis of the Mac's OS for almost 10 years, and though it was showing a little bit of age as it progressed, it was still a remarkable OS.
Hire a Linux system administrator, systems engineer,
He's thinking about when Apple went from Motorola 680x0 chips to PowerPC ones. The OS had a 68k emulator that allowed it to continue to run old apps. The poster is expecting that if Apple releases an OS on x86 hardware, the OS will include an emulator so granny won't then wonder why her old recipe application doesn't work on her new computer.
As someone who's been if a few multi-architecture operating systems (BeOS, OpenStep, NEXTSTEP), I can say that it isn't as pleasant as everyone says. While OpenStep made it pretty easy to cross compile, there were always apps that just weren't available for your platform (particularly NEXTSTEP for HP Apollo machines.) It's not a good place to be, and it is always frustrating for users. How many PPC BeOS apps were there when the BeOS stopped being something a lot of people did? Certainly not as many as there were for Intel.
My basic point is that it will be a major pain in the ass for all of the users for gains that aren't yet a big enough deal to convince me.
There should be a moratorium on the use of the apostrophe.
Max V.
NeXTMail/MIME Mail welcome
You put out a lot of good reasons the Open Source community would want this, or could use it. But you're putting in no reason for Apple to want to do it.
.09 (Or is it .06?) micron fab IBM just built that'll produce the next generation of Apple chip.
Apple would die the quarter that OSX became an x86 commodity. On x86 hardware, they'd be dealing with all the vendors that make things for Microsoft as competition, and dealing with unhappy traditional Mac developers that just made the switch to OS X on PPC. They'd alienate the entire Apple infrastructure just to gain a few points on hardware speed that they wouldn't even be able to sell anymore. People won't pay Apple's -slightly- higher hardware prices when they can get the exact same thing (technically) for less.
Apple makes money by selling hardware, that's where the support base they have is, and that's where the company excels. The entire user experience as a whole is what drives Apple sales.
If we do see OS X on x86, we'll see it on the same Apple hardware we see today, just with a different chip in the mix. It'll all be Apple branded, no clones, no over the counter OS sales for plain-jane x86 machines.
This is the ONLY way that an x86 port of OS X makes sense to Apple.
Personally, I'm betting that it'll be the new
My own pointless vanity vintage computing page
Hello.. please stop staring at your cock, and please in future read posts before you attack the poster.
;;winces, hits submit;;
Furthermore, your assumption that PPC is automagically more powerful than Intel architectures is a clear indication that you are severiously under-informed.
Note that the poster you responded to never said the PPC was more powerful than intel. They referenced the fact that when apple changed from 68k to PPC hardware, they included an emulator so that legacy apps could be run on PowerPC computers. The emulation he referred to was for third party apps which have yet to be recompiled, not for the ported OS.
All the original poster said was that while it was no big deal to emulate the 68k on the vastly more powerful PPC, emulating a PPC on an x86 would be not so easy, as x86 and PPC are roughly equal. I am not able to see where your rediculous ad hominem attack comes from. They did not even advocate PPC as more powerful than x86.
That being said, it would indeed be extremely difficult to emulate PPC on the x86! This is simply because of the way the chips are designed. The PPC is RISC; it has simple instructions and lots of registers; the x86 is CISC; has few registers and complex instructions. RISC is not necessarily better or worse than CISC, and the x86 is not necessarily better or worse than the PPC. However, it is generally well-known and accepted fact that it is easier to write an emulator that runs on a RISC machine than a CISC one, and it is quite obvious to anyone who is familiar with the emulation scene that the PPC and x86 are good at different things, and one of the things that the PPC really shines at is emulation.
This will become blatantly obvious if you consider that there are multiple, at least three, separately developed programs-- one of which is open source-- which emulate an x86 PC on a PPC Macintosh. There are, however, no extant PPC Macintosh emulators for the x86 PC. None. And it isn't for want of trying; you can see here that there have been a number of macintosh emulators for the PC, just that none of them have done PPC emulation, only 68k. There have been many attempts to emulate the PPC on the x86, it is just that they have all come to nothing-- becuase the architecture of the two machines is simply such that it is relatively easy to emulate x86 on PPC and relatively extremely difficult to emulate PPC on x86.
I suspect i am responding to a troll. I really ought to submit this as AC. Oh well..
Irritable, left-wing and possibly humorous bumper stickers and t-shirts
You forget that, due to the nature of Apple's solid APIs and the fact that OSX is BSD based...
All the developers will have to do little more than re-target and recompile. Very little work involved, relatively speaking.
Why would a Carbon app need to be significantly modified to compile on an x86? Does an app for Solaris SPARC need heavy modification to run on Solaris X86? No, it doens't, it needs, well, no modification whatsoever, it just compiles.
Same thing here.
Yes, they would need a new emulator for classic apps.. but many of these already exist for x86, they could probably purchase code if they don't want to do it themselves. it would be no harder than writing one for PPC. PPC and 68K do not have any kind of inherent compatability.
Actually, apple released an incomplete build of an early development build of OSX compiled for X86 to ADC members sometime around 4 years ago. It was dubbed as the Apple Rhaposody OS Developer Release 3. It was quite intersesting to pick up the similarities between it and OSX. A ton of information, along with screenshots are posted at this site.
It was really a transitional OS which gap between NextSTEP and OSX. It contains both elements of both OSes. Anybody recognize the chess program at the bottom of the page?
-- If you try to fail and succeed, which have you done? - Uli's moose
Back when PC boards were designed with red, blue, and black tape on mylar sheets, and UARTs were the cutting edge, there were two vendors of UARTs who had somewhat different designs. A small manufacturer of terminals had designed for one of 'em. But they were new and cutting edge, and the plant capacity was limited. So the vendor was being obstinate about giving them sufficient allocation to make their production targets.
Well the alternative chip was about the same side and functionality but had different pinout. And there was some extra room on the board. So a few days before the salesman was due to visit they hauled out the mylar master for the PC board, laid out the pad pattern of the alternate chip, and started taping up something that looked like reasonable circuitry.
Sure enough, the salesman saw the work in progress, concluded that the terminal was being designed so it could be built with either UART, and paniced. After that there was never a problem getting allocation.
I think the circuitry was never finished and tested. The pads made it onto the final PC board (no point in ripping the tape back off the master) but weren't even dirlled (at 1/2 cent per hole per board). And they came to be known as "The Blackmail Pads". B-)
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
Of course Apple have a x86 port of OS X. They want to keep their options open, and even if they don't move to x86 they will benefit by having an operating system that is already portable between architectures.
/Applications /DVD Player.app /Contents /Frameworks /DVDPlayback.framework /Versions /A /DVDPlayback | less "
l ePIVSupport
As for the evidence - it you do a "strings
(i've added spaces before each "/" to keep slashdot happy - you need to take them out again!)
Now, search for "Debug", and look at the three next lines:
DisablePIIISupport
DisableATHLONSupport
Disab
Now why would Apple's DVD Player have code concerning itself with PIII's, P4's and Athlons if they didn't have a version which ran on those chips???
Personally, I don't see Apple making the switch, but they've survived by surprising us time and time again...
The kernel is called xnu. The Darwin operating system (like most *BSD distributions) is comparable to what RMS and Debian call GNU-Linux. MacOSX uses a fork of Darwin-- there isn't a one to one correspondence between a Darwin release and a MacOSX release-- and adds further libraries and services, Carbon, Cocoa, and Quartz being the three most famous.
Apple employee Vince Garcia once mentioned he had OSX running on an Intel at home back in 2000, nothing new here. And remember all those stories on Macworld of the old Mac OS ports running on Intel? Heck, I'm running OS7 right now, albeit via Basilisk.
Apple will NEVER (read: NEVER, NEVER, NEVER) sell a version of the Mac OS that can be run on any cheap POS that you cobbled together from parts you bought in Target for $5 each. Wake up and smell the coffee, okay, because I'm getting tired of reading all your posts.
Apple sells the experience of using tightly-integrated hardware and software. They can't do that if they suddenly have to make sure their software will work with every home-built x86 whitebox on the face of the earth. What Apple does is something that Microsoft can never do, unless they start selling their own brand of computers and restrict Windows to only run on Microsoft PCs.
Even if Apple ever were to switch to making x86-based Macs (and you, the reader, are significantly more likely to bang Anna Kournikova than to see an x86-based Mac for sale), they would put something proprietary in those machines, maybe even in every component of those machines, and change the Mac OS to refuse to boot if it doesn't detect that proprietary something. That's the only way they'll be able to preserve the 'it just works' aspects that are a major part of their success.
Personally, I think Apple will,very soon, tell Motorola to go piss up a rope (and I say, it's about time!). The new IBM chip has something close enough to AltiVec, and IBM actually gives a shit about improving their products. Now that Mac OS X is truly ready for prime time with 10.2, all Apple needs is to be able to produce machines that will impress the MHz/GHz-obsessed, cock-measuring crowd.
~Philly
I think the advantages of actually putting out an x86 version of os x (which by the way went by the name "Star Trek" before, IIRC) are outweighed by the various (mostly hardware-revenue related) disadvantages.
However, it's an invaluable asset to have anyway, because you can blackmail microsoft with it. Remember when MS bought all that Apple stock? Remember what dire straights Apple has been in in the past? Despite all that, Mac OS remains to this day the only consumer OS besides windows that has managed to gain and hold onto a significant userbase versus Windows. And it has a lot of software. So pretend you're Bill Gates, and Steve Jobs gives you a ring and says "If we start to go under, for any reason, we're releasing our x86 build of Mac OS X... as open source." There's not enough TP in Redmond to handle that kind of threat. Or any of the lesser ones they could make too.
---If you can't trust a nerd, who can you trust?
Actually there is an Intel port. There has been for years. Way back in the Rhapsody days there were two developer releases available for Intel. Just because they stopped making them available doesn't mean they stopped building it.
The biggest reason is that maintaining an Intel version ensures that everything they write stays reasonably portable. It they can stay compatible with PPC and Intel in the code, than supporting any other chip that comes along can't be much more difficult.
Internal builds used to always be built fat...they would just be stripped to PPC-only when it came time to press to a CD for external use. I don't know if it's still the case, but I don't see why they would stop the practice.
Also, maintaining compatibility keeps future migration options open to them.
Most of OS X is highly portable already. The kernel is Mach, which was fundamentally designed with portability in mind. Above that is the BSD layer which is regularly synched with the OpenBSD source tree, which is x86 code -- so it's portable. CoreFoundation is part of Darwin, so it already compiles on x86. Cocoa is very high level and used to run on x86 back in the OpenStep days...no big issues there. I see no reason why Cocoa couln't easily go to Darwin as well. Apple had to basically build the Carbon library from scratch after the developer community refused to migrate en-masse to Cocoa. I don't believe Apple would be short-sighted enough to not write it in a portable fashion. Really, Classic is the only part of OS X that would cause a problem with an x86 port. If push comes to shove, Apple could just draw a line in the sand and say that Classic isn't supported...developers have had enough time to move their stuff forward.
Of course, just because the port is possible doesn't mean that Apple will ever make it a product. Support for such a thing would be a nightmare given the huge number of hardware options in the x86 world. Apple is barely capable of keeping up with drivers for there exremely limited set of hardware options.
Nobody said anything about emulation. A port is a native compilation, and therefore no performance hit is taken.
This is a quarter-truth. However, you're ignoring a fair number of issues:
* A port would likely be less tweaked for the architecture (run out of registers more likely, cause cache misses, whatever) for some time.
* Apple didn't port all of the MacOS to the PPC for *ages* (actually, I'm not sure the entire OS ever went native). They just ported critical chunks, and emulated less used bits. If you want to avoid emulation, you're looking at a much larger porting task in a short period of the time.
* Apple could port the OS -- but 99% of applications won't be recompiled for the x86. That means a lot of apps need to be emulated.
Furthermore, your assumption that PPC is automagically more powerful than Intel architectures is a clear indication that you are severiously under-informed.
Actually, he's right, though he simplified things a bit. The PPC has far more registers than the x86 architecture. Any emulation would involve extremely expensive swapping of registers very frequently. I'm don't remember what L1 fetch time on the x86 is, but it's at least one cycle. That means that your PPC code is going to run, at best, at half speed a fair bit of the time.
The reason the PPC could emulate the 680x0 so efficiently is because it had so many registers and didn't have to execute many instructions to handle any single 680x0 instruction. Also, the PPC was a faster chip, so running slow 680x0 code still seemed reasonably peppy to the user -- trying to port PPC code to the x86, a *competitive* line, means looking at some serious slowdown issues.
I won't go so far as to call you a newbie, but your bias suggests that you have a ways to go before you become a seasoned professional. Keep on plugging though, and try to be more open-minded. Consider doing research before forming conclusions, for example.
I think that you owe it to the parent poster to do the same yourself.
May we never see th