Asus Corrects Eee PC Source Code Issue 157
ozmanjusri writes "Asus has corrected the availability of source code for its Eee PC, and reaffirmed its commitment to meeting the requirements of open source licenses, including the GPL. They also announced the upcoming release of a new SDK to assist the Open Source community development on the Eee PC."
What's With the Name? (Score:4, Interesting)
They're going to release the SAME code, right? (Score:1, Interesting)
I see this quite a lot... companies admitting their guilt, and then releasing "cleaned up" source code that complies with the license(s) in question.
The problem is that "cleaned-up" source code creates a different set of binaries, for which source code must also be released.
They need to release the SAME source code that was used to create the binaries which they've already released and distributed, not just "cleaned-up" code, which generates different binaries.
As a company that "Sells" Open source... (Score:5, Interesting)
That Extra Mile (Score:4, Interesting)
NOTE: I have asked Asus about enterprise encryption support and they have said it may be coming. I have also asked about the madwifi source but received no definitive answer yet.
Re:What's With the Name? (Score:3, Interesting)
Last minute changes (Score:3, Interesting)
As I understand it, Asus used a new chip to meet the cost targets and had to make some last minute code changes to get working systems out the door. No 'cleanup' of proprietary source, no trying to hide stuff. Over at the eeeuser forum, they are already reporting successful recompiles of the source and use in a different distro install on an eee. Delay due to oversight is the simplest explanation (huh, ever heard of Occam's Razor?). All you conspiracy hunters; find a new playground!
I hope not these three (Score:3, Interesting)
These are trademarked by M$, Asus would get into serious trouble.