Insofar as one could consider the kernel to be the core of an operating system, this (specifically, XNU on ARM) is the core of iOS. Having the Darwin userland atop that is simply icing on the proverbial cake.
What would you consider the core? Is it UIKit? Cocoa? libc? SpringBoard (the homescreen application)?
I'm always happy to see open work happening on Darwin. I wish I could easily install an open Darwin OS as viable as say, ArchLinux alongside OSX, so that it maintains the same benefits such as energy usage, and dtrace, and whatnot. My dream: a BSD/Darwin with a lightweight accelerated framebuffer compositor such as Wayland.
On the desktop we can install OS X on non-Apple hardware to make Hackintoshes. So far this is just a kernel port with no graphics, but will it lead to installing iOS on non-Apple phones in a similar way? 'iClones'?
Hackintoshes are largely possible because it's possible to get almost the same components used in Macs on regular PCs. It might be a little more difficult to get your hands on the chips Apple uses in iPhones/iPads (not to mention cobbling them together). Not that doing so wouldn't be pretty awesome.
No, this is Darwin which is the open source part of iOS / OS X. I would imagine iOS looks for some pretty specific set of things from the chipset it is running on and there is no "generic ARM phone".
that's quite an achievement and great news!
But looking at it from a more practical viewpoint; why run darwin if you can run linux on arm and phones already? Even on iOS itself, with a jailbroken phone you can ssh into the underlying OS and execute arm binaries through the shell.
I can imagine it's a stepping stone towards running iOS in QEMU for running apps on your desktop or tablet, which is nice as I could run my bought Eclipse, Tigris and Tikal boardgames on my desktop. I am not sure if I'd break the EULA in that scenario.
Not every phone has a jailbreak available for it. Plus, you're still stuck with an effectively sandboxed kernel. You can't fix any bugs or implement any kernel level drivers, for example.
If I need a new IOKit driver class, I simply build the kext and use `kextload`, or I can just prelink it into the kernelcache.
[+] [-] bsimpson|12 years ago|reply
[+] [-] DHowett|12 years ago|reply
What would you consider the core? Is it UIKit? Cocoa? libc? SpringBoard (the homescreen application)?
(Edited: s/Darwin/XNU/; thanks shibby!)
[+] [-] lloeki|12 years ago|reply
[+] [-] winocm|12 years ago|reply
[+] [-] clarky07|12 years ago|reply
[+] [-] ihuman|12 years ago|reply
[+] [-] billyjobob|12 years ago|reply
[+] [-] garretruh|12 years ago|reply
[+] [-] protomyth|12 years ago|reply
[+] [-] fsiefken|12 years ago|reply
[+] [-] winocm|12 years ago|reply
If I need a new IOKit driver class, I simply build the kext and use `kextload`, or I can just prelink it into the kernelcache.
[+] [-] monological|12 years ago|reply
[+] [-] sleepyK|12 years ago|reply
Even if it were possible, it would take a hellish amount of time to get working, I'm sure.
[+] [-] eonil|12 years ago|reply