Post a Comment
So ist it possible to have the Hardware of say, a MacBook, fully supported, while not giving up any of the 4 freedoms which should come with software, by using Darwin+GNU+Xorg+Gnome/KDE/Whatever?
And by full hardware-support I mean EVERYTHING more or less out of the box. Hotkeys, webcam, suspending, you name it.
Has anyone experiences with that or are there tutorials how to achieve this on the web?
"So ist it possible to have the Hardware of say, a MacBook, fully supported, while not giving up any of the 4 freedoms which should come with software, by using Darwin+GNU+Xorg+Gnome/KDE/Whatever?"
No because The new licensing does not permit that.
http://apple.slashdot.org/article.pl?sid=06/11/13/1120215
Look at the new APSL Rules where your license to their source can be revoked at any time.
RE[3]: Full Hardware-Support + Freedom?
"The Apple Public Source License (APSL) version 2.0 qualifies as a free software license."
http://www.gnu.org/philosophy/apsl.html
i tried doing that with a g4 powerbook and darwin 8. all i can say is good luck! a bunch of drivers that ship with darwin are binary only, such as the broadcom ones. on top of that there are no apps in userland to configure wireless. never got x to work either. i'm not even sure if they include suspend support in darwin. maybe i should try again.
Simply put, no.
Darwin != Mac OS X, rather it's the kernel and much of the base, system level userland. But you won't find things like the Finder or the Dock, or even the windowing system in the source code.
It's more like a basic BSD distribution, but without as large of a ports directory.
There was an OpenDarwin initiative going on awhile back, but they closed up shop because of a lack of enthusiasm, and not really wanting to be a host for Free OSX projects. The only real reason Darwin is good to have open is for debugging and educational purposes, and of course for people to write drivers for those of us who go the Hackintosh way...
This is a good move by Apple, but sheesh, the license is verbose!
Given that much of the code comes from FreeBSD anyway, would it have been difficult for them to have released this code under a BSD license? I wouldn't have thought that would be much of a "risk" to them, but I may be wrong.... :-)
Anyone else think the license is too long, and a BSD license should have been used?
What are you blathering on about - Apple claims that they use code from FreeBSD - in other words, Apple has pulled code off the FreeBSD, not FreeBSD submitting code to Darwin.
Its a know fact that XNU uses BSD code in there, and it has been updated over the years using the latest FreeBSD code - and Apple submit the changes back, NetBSD incorporating a lot of the msdosfs improvements - for example.
In fact Steve is using BSD as base since BSD4.4 in NextStep and there is even some NetBSD code in it. Sometimes Apple is even commiting some code to FreeBSD (some Apple developers have got commit right in FreeBSD), some weeks ago for example (MAC). Nothing unusual, but it doesn't fit to the usual theories about the evil scheme of these big companies ;-)
Don't really understand why this matters one way or the other. You release the updated source to something which is not being used in previous versions because its essentially unusable. So what?
Maybe it allows Cupertino to more plausibly offer the party line that in some way OSX is more open than Windows? Not that it is, its just differently but equally closed. That is one of the party lines one comes across. Is that it, is it just a marketing thing?
I was hoping to discover from the comments what we can use this for, but the answer still seems to be nothing.
The Darwin source code is entirely usable (it's not crippled in any way), it just doesn't get a lot of use. Does the lack of users make the code less open? APSL 2.0 is an OSI-certified open source license. You can download the code, modify it, distribute it, include it in your own programs, etc. The Windows source code is only available under a Reference license, to businesses or academic institutions who pay for the privilege. They are not "equally closed" by any stretch of the imagination.
I think this was a good step.
The developers can optimize the drivers for the kernel in a better way, because now they can look into the source code and match the drivers really smooth to the kernel.
Also it offers the possibility that bugs could be found in the code because now a lot of more eyes are looking at it.
In my eyes a opertunity for a higher quality for apples custormers.


