Post a Comment
Its been awhile since I've seen you post around here Moulinneuf, I'm sure everyone has missed thoughtful and insightful dialog like
"Your a **BSD** , you have no credibility at all"
"2) **You** are fast at burning someone. Other's like me just reply in kind , to your intelligence lacking insulting and unrealistic and fabricated reality that is completely unrealistic."
"3) Your a liar , traitor , coward and incompetent. "
"I apparently , also need to actually point to you and take you by your childish hands , that Opening and freeing the source code will enable BSD and other OS to be run properly and correctly on this device and the hardware it's made of."
In a single post, you managed to break rules 1-4 and rule 6 of the OSNews forum rules (http://www4.osnews.com/docs/rules). I have to admit, I do love reading your posts though, especially the wild, barely comprehensible meltdowns about BSD.
Edited 2007-11-28 17:17 UTC
Seriously, what was the story here? Traditionally, whenever companies have appeared to be contravening the GPL, the FSF in particular have generally given them time to sort things out. Usually, as in this case, things turn out OK.
While it was good that people found out about this, I found the ranting a bit distasteful. Let's give a company with a decent product, who is putting Linux on an awful lot of desktops incidentally, a bit of slack.
RE: What was the Story?
now everybody who was bashing them, can crawl back into their holes.
Well, actually - their website still sucks as I mentioned in the previous article comments. It's still difficult to find recent drivers and BIOS updates for some products.
I'm also dreading a call to ASUS to resolve my recent hardware problem on a barebones box that just died. I suspect it will be more productive for me to simply buy a new PSU and/or motherboard and hope that it resolves my "dead machine"... because last time I contacted their support I got the runaround, finally got an RMA # to send them my motherboard, they proceeded to send it back without fixing it, and then asked me if I wanted to pay to ship it to them again to fix it.
So, I feel entitled (as a dissatisfied customer) to continue bashing ASUS for their crappy website and lackluster support - thank you very much.
edit: added a missing word.
Edited 2007-11-27 23:09
Why should you wait at all when you can get one right now (no waiting), for $99 less cost, with the more secure and malware-resistant Linux installed, along with a complete set of desktop applications that won't come with XP?
Where exactly is the upside for crippling the machine with XP and thereby and making it more expensive, more vulnerable and less capable?
For people that use applications that are only available on Windows, Linux is less capable. Part of the attraction of this particular product for me is being able to edit and mix audio and program drums and soft synths. I can't do that in Linux with the (superior) applications I use.
A 900Mhz Pentium M-based Celeron is fast enough to handle light duties for audio while on a train ride.
Sadly, Linux audio tools are still far behind what's available for XP and OSX.
Just one example. I could go on......
Point being is there is a time and place for Windows, at least for now.
I thought XP was sort of on the way out of being sold to distributers because vista was out?
Well, that would make it imposssssible to run windows on the Eeee then, for sure.
Not yet. It was previously Jan. '08 for the cut off to OEMs, but that has since been extended to June '08. Thank God for that!
The default window manager is IceWM, customised to fit the screen with a tabbed interface.
The full set of KDE libs are installed, though, as most of the apps are KDE apps. All you have to do is install kcmserver and kicker via apt-get and modify the X startup scripts to get a full KDE desktop, though.
The full set of KDE libs are installed, though, as most of the apps are KDE apps. All you have to do is install kcmserver and kicker via apt-get and modify the X startup scripts to get a full KDE desktop, though.
Thanks for the info
The main attraction of GPL code is that it is publicly available. Anyone can just grab the source code & use it. The source code is published.
For anyone who has used GPL code in their product, and they are subsequently accused of GPL violation ... the remedy is a classic "no brainer". Just publish the sorce code as you used it. All accustaions instantly vanish.
After all, it was already published when you got it in the first place, so where's the harm? What is the downside of GPL compliance?
Monsoon multimeida showed how that "no brainer" decision worked a few weeks ago. Before them, Parallels made exactly the same choice. Now ASUS have shown us again.
As I said ... a no brainer.
Edited 2007-11-27 23:37
The madwifi project is dual-licensed under GPL/BSD, so Asus is not obligated to provide corresponding source code for their modified ath_pci driver. For the time being, the binary driver that ships with the eeePC is the only way to get the wireless chipset to function under other Linux distributions.
Maybe if a lot of eeePC users ask nicely, Asus will release the source. But under the BSD, the distributor ultimately has the legal power.
Because the 2-clause BSD licence (also known as the modified BSD licence) is compatible with GPL?
That only means you can put BSD code in the kernel or in Linux drivers. But once the code is there only the GPL applies. You can't ship a binary driver and refuse to publish the source because it's dual GPL/BSD licensed.
The atheros sources they use are probably available in the zip-file on their site or from xandros though.
Edited 2007-11-28 08:55
There are two links: the proprietary HAL to GPL/BSD driver and the resulting object to the kernel. How the licensing works depends on whether the distributor or the user performs each of these link steps. The only way the driver can be distributed under the GPL is if the user does both links. If the distributor does the first link, then the result may only be distributed under the BSD, and the user must perform the second link. The distributor cannot ship a completely linked kernel module as this is a violation of the GPL.
I'm not familiar with how Asus handles this situation. It could be as simple as automatically running a script on first boot. But they could be violating the GPL if they aren't doing something to cause the linking to become the action of the user rather than of the distributor.
yeah but if they build it and distribute its not exactly a separate work, as it "links" with the kernel, which btw, is GPL.
also, if they havent released the source for modified madwifi driver, this just goes to show how asus are complete moron mongers, as they simply do the bare minimum, even though its completely a disservice to the customer, and wouldnt hurt them in any way to do.
Didnt they just in this answer to community mentioned that if customers feel that something is missing, they should email Asus and ask for it?
Asus isn't trying to rip anybody off, it's just that they dont have a clue about the software side as they have outsourced it to Xandros.
"Everyone can put their "You bastards!" back in your pocket now."
If Asus is willfully tivoizing the hardware then yeah it would be discriminatory against users and they might be rightfully so labeled. It's bad that they have to pay blood money to MS every sale they make.
MS is more or less slandering and racketeering GNU/Linux and they need to be made accountable. Don't expect the USA to help out if MS is riding shotgun on a trade or defense agreement with Taiwan. Perhaps the only way to deal with these issues is to put pressure on Asus and the Taiwan govt. by taking face away from them.
http://arstechnica.com/journals/linux.ars/2007/11/27/asus-resolves-...
"In response to criticism from Linux enthusiasts, Asus has made additional source code archives available for download with code for the asus_acpi module, BusyBox, and several other components. The code released by Asus brings the company into compliance with its obligations under the GPL and should satisfy most of the critics."
http://support.asus.com/download/download.aspx?SLanguage=en-us
" Version 701 2007/11/24 update
Description ASUS_ACPI Source Code
File Size 27.73 (KBytes)
Download from Global USA Europe China Japan"
...
meanwhile
...
http://www.fresnobee.com/263/v-printerfriendly/story/187043.html
"Fresno Unified officials buy 1,000 wireless laptops that will fit on students' desktops."
Interesting.
Edited 2007-11-29 09:04






So MS decided to extend support.