Slashdot Mirror

← Back to Stories (view on slashdot.org)

Asus Corrects Eee PC Source Code Issue

Posted by ScuttleMonkey on from the learning-from-mistakes dept.

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."

7 of 157 comments (clear)

  1. What's With the Name? by Apple+Acolyte · · Score: 4, Interesting

    EEE? Triple E PC? What's with the name (i.e. what does it signify)?

    --
    Part of the hardcore faithful who believed in Apple long before it was cool again to do so
    1. Re:What's With the Name? by Entropius · · Score: 2, Interesting

      Asus has a history of making good stuff (I'm typing on an Asus laptop at the moment) but with occasionally wacky names and marketing phrases.

  2. They're going to release the SAME code, right? by hacker · · 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.

  3. As a company that "Sells" Open source... by houstonbofh · · Score: 5, Interesting

    I work for a company that provides Open Source solutions. We are actively involved in several FOSS projects, and support the concept any way we can. That said, with the rapid advances of the base projects, and our changes to those projects, it is very easy to let publishing the source slip down the priority list. I have forgotten several times, and this has been on projects I develop for! (I fix it as soon as I realize...) I would bet many omissions can be attributed to overwork, and not malice.

  4. That Extra Mile by tundra_man · · Score: 4, Interesting
    I have noted in the last few days the release of the various bits of source code and am happy to see Asus ensure that they are in compliance. Now I would love for them to go the extra mile and release the code changes to MadWifi to support the wireless. I know this is released under a BSD style license and they are not obligated but one of the biggest weaknesses of the Eee right now for me is the inability of their wpa_supplicant to offer enterprise encryption support. Something that is hard to change without the MadWifi source or switching to use NDISWrapper. The Eee is the best gadget but I want my wireless @ work.

    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.

  5. Last minute changes by Anonymous Coward · · Score: 3, Interesting

    Full Disclosure.....I haven't received my eee yet, I ordered it last Wednesday and it is due to arrive this week. I can't logon here at my client; my nick is alanbcohen

    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!

  6. I hope not these three by someone1234 · · Score: 2, Interesting

    Embrace, Extend, Extinguish.

    These are trademarked by M$, Asus would get into serious trouble.

    --
    Patents Drive Free Software as Hurricanes Drive Construction Industry