Linux Unwired
Infrared, Bluetooth, 802.11 (in current a, b and g offerings, 802.11i is also being discussed), wireless access points friendly to Linux, United States commercial cellular networks and GPS systems are all covered in a single title that surprisingly fits all of this information into 284 pages. All the chapters can be subdivided into two large parts - familiarizing yourself with the technology (the primer on GPS is pretty good) and running Linux on it (with code and shell command samples and lots of URLs).
Introduction
The authors start up with introduction to wireless, intended for Linux geeks who are not quite up to speed on radio technologies. The concepts of waves, spectrum and radio wave behavior are explained, so later the reader can explain what a retracted radio wave is. Then the first chapter moves on to explain antenna behavior, wireless infrastructure modes and some common problem, like a hidden node in ad-hoc infrastructure. The chapter is well-written, and you're not expected to have an advanced radio degree or ARRL membership to understand the terms.
WiFi cards
Chapters 2, 3 and 4 deal with connecting a Linux desktop or notebook to a wireless 802.11 network. The first issue is that of chipsets used in the wireless card, and even though enough research has been done already, authors discuss different quirks relevant to Intersil Prism, Lucent WavelLan/Orinoco, Aironet/Cisco, Symbol, Atmel, Atheros and Broadcom chipsets. We need to discuss chipsets instead of discussing the actual wireless cards, since some hardware may be shipped under the same brand name with different internals. "A good case in point: the D-Link DWL-650. This radio card initially shipped with a Prism II chipset and was very popular, because it worked on a Linux box. However, D-Link changed chipsets when it released the DWL-650 Version 2, choosing the ADMtek chipset. It is very difficult to tell from the packaging which version of the DWL-650 you are purchasing".
The chapters are done in traditional walk-through mode. They are not HOWTOs or compendia of reference information, available from the manufacturer's Web sites. The authors made an effort to ensure the reader is capable of starting up a wireless connection on Linux box, knowing nothing about it while learning important technology in the process. Certain wireless drivers need to be compiled into Linux kernel, so the task is not for the meek, but with detailed explanation, plenty of URLs and nice fonts and paragraph formatting O'Reilly Publishing uses to differentiate between the text, commands entered at the shell, and URLs, the book is easy to read.
Chapter 3 (available in PDF) teaches the reader how to connect to existing wireless network once the wireless card has been recognized by the system and proven functional. By the time the book hit the stores it was already a bit out of date, since the very first hotspot operator, Cometa Networks, shut down in May 2004. Chapter 4 discusses wireless security, touching WEP settings, a $20 Linuxant utility allowing the user to implement WiFi Protected Access, as well as authentication utilities wpa_supplicant and XSupplicant.
WiFi access points
The issue of WiFi access points is not trivial either, as many vendors out there will ship the product with a Windows app being the only way to set it up. However, for the access point setups that are Web-based, a browser in Linux will do the job. The most Linux-friendly access point include Linksys, Netgear, D-Link, Cisco, SMC, EnGenius, Belkin, US Robotics, Microsoft and ActionTec. Again, harsh reality kicked in between the time the book was written and went to press, and it's sad to see yet another Linux-friendly access point vendor quitting the market.
Not satisfied with commercial offerings out there? Chapter 6 takes the reader into the task of building your own access point. Don't forget that an access point doesn't need to be a compact portable - your old 486 with Linux on it and a wireless card connected to it might serve the purpose. Unfortunately, after all the hardware is bought and assembled, the final product might still cost you the quadruple (in case you go with smaller form-factor motherboards and CompactFlash cards for software storage), so consider this more as a geek project, not a viable solution. The authors use LinuxAP distribution for this task.
16 pages are dedicated to hacking Linksys WRT54G access point with Sveasoft, described as disruptive technology by Robert X. Cringely. The authors also take a brief look at Wifi-box and OpenWRT.
Other wireless technologies
Bluetooth, Infrared, cellular and GPS chapters follow the same chapter plan - first the basics of the technology and simple use case scenarios of what you might use it for, then the hardware needed to implement the wireless technology, available Linux software to do the jobs, accompanied with the list of shell commands to successfully talk to a wireless product, and after that typical applications of the working link.
The authors tested various wireless data plans in the United States, although this data, once again, is constantly changing as the operators buy one another and introduce new data plans. The winner of the quality and the fastest download tests, by the way, was a Motorola v120e phone on Verizon Wireless network. In upload speed tests a Merlin C201 PCMCIA card on Sprint PCS network won. T-Mobile also offers a PCMCIA card for its GPRS network, so the authors install and run it under Linux in Chapter 9.
The last chapter discusses using Linux computers with GPS devices and open-source GPSdrive project for reading GPS data.
The book
For those just venturing into the wireless world, the book would be useful. All the information provided on WiFi connectivity can perhaps be googled and found in various HOWTOs. With wireless operators, GPS systems and Infrared connection one would have to rely on enthusiast sites and newsgroups. Having such informative title that covers all of the technologies would be very useful to a Linux enthusiast.
With that, the book can be quite overwhelming, although it's probably not intended to be read from page 1 to the end. There's usually more than one correct way to do things in Linux, and for each successful project another competitor appears on SourceForge the next day. I like the authors' approach of dedicating most of the chapter space to one, leading, Linux package that seems to be dominant in the field, and then briefly mentioning the others. A notable omission is Intel's Centrino drivers for Linux, as the company is bound to become a leader in the chipset marketplace with 42% of notebooks shipped in 2003 running Centrino chipsets.
But overall the book proved to have a high informational and educational value, not only you follow the steps on setting up wireless technologies on Linux, but you also learn the internals of the technology and why certain things are done that way, but not another.
You can purchase Linux Unwired from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, carefully read the book review guidelines, then visit the submission page.
Get an airport(or as I have, an AirMac) card!
/ducks!
From the article --
Microsoft disputes the notion that there's a problem with the way Windows XP works with Wi-Fi.
That's a blatant lie, typical Microsoft attitude.
For the longest time, the wi-fi connection of my notebook would keep dropping and I thought it was because of a bad wireless card.
I changed my wireless card, I tried everything possible.
What I had not noticed was everything I was in Linux, this never happened - no matter what! There are areas in my school where the wi-fi signal strength is particularly weak, and even in those areas I never lost connection from Linux.
Somehow, when I would boot into Windows, my wi-fi link would keep dropping. I still haven't figured the problem yet, I just use Linux instead everytime.
And so contrary to what Microsoft may say, there is a problem with Windows XP (I have the problem whether am on XP Home or XP Pro). I wonder whether they EVER admit their mistakes.
I knew he was going to rate the book an "8"!
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
The problem is if Windows can find a network that broadcasts it's SSID when yours doesn't, it will try to switch. There are three (or four) soltuions.
I REALLY hope that they fix this in SP2, because it's my number one complaint.
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
Don't get me wrong, I'm not a luddite and I think these are great technologies, but for myself they just seem expensive and not terribly useful. What I do find interesting is use of WiFi for rural broadband. But that's still pretty novel.
You all know that the puppet isn't real right? Maybe it is just a pet peeve of mine, but it drives me nuts when people refer to fake people/things on TV like they really exist. You know, like the cast of Friends, cast of Star Trek, Ralph Nadar, etc.
I Am My Own Worst Enemy
I was one of those users who read about DWL-650, went to buy one and came back with a DWL-650+ without noticing it. It sucks. At my Computer Sciense Departament (like 12 AP), my laptop gets frozen because the driver and the computers turns very unstable. At home it works well because I have only one AP. Wireless tools are very primitive also. You can't scan networks not being root. I started writing a KDE tool emulating the funcionality of the new Win XP Service Pack 2 wireless tool but libiw is a pain. I ended importing a patched sources (from some Ximian guy) to use it. Still havent figured how to scan available networks being a user. Design flaws from a server oriented operating system.
I suppose the eTLA that's applicable in such a circumstance is "WTFTV".
Does anyone else have problems under linux with a DWL-G650 (802.11g) card using the Linuxant drivers? I'm using the latest drivers from DLink, but for some reason randomly, the device just stops working, but looks like nothings wrong. The device is still 'up', the lights are blinking normally, the routing table is still okay, and no errors in the dmesg, syslog, messages, it just stops working, can't ping the ap or bring up websites. I have to do quite a bit to reinitialize it (so much that I created a script to do it for me). Does this happen to anyone else?
Things you think are in the Constitution, but are not.
After going through many different drivers and kernel compiles, I Later found that some 650's not only have an ADMTek chipset but some also have be a Realtek chipset. After trying the ADMTek drivers I found my particular card had a Realtek chipset and it came right up using the ndiswrapper driver using the windows Realtek driver (the driver supplied by d-link on the cd would not work. I had to get the windows driver from Realteks site). The thing works like a champ now with Fedora core 1.
I am an avid unix/linux user and I pretty much prefer to run my boxen in non-Windows mode. I also am an information security professional and use many tools such as Kismet to do wireless discovery. After much reading and research I decided on a Cisco/Aeronet card as my card of choice for both sniffing and wireless use in Linux. Well low and behold once I got the Cisco card, which was stated as being supported in the OS, I managed to get it installed and compiled to be used as a sniffer but to date and after a solid year of trying I have not been able to get the damn thing to work as just a network card. After months of frustration I finally gave up and went and bought an Orinoco card that I thought I would use for both sniffing and network access. Again, I managed to get things compiled and working this time with network support for the Orinoco card and no ability to sniff. Although both vendors claim full functionality within Linux I am to date still carrying around two wireless cards to get the job done. Sadly, when I boot Windows and plug in either card in XP they both seem to just work. Ah, the bitter irony.
Believe it or not I do remember... Because it's still playing ninety fucking times a day!
1.) Get a 'high-falootin' title (PHD, MSCE, etc).
2.) Paraphrase information freely available on the net.
3.) Blow college professors and get them to use it as a text book for their class!
5.) PROFIT!!
Easy guys, I put my pants on one leg at a time. The difference is after I put on my pants I make gold records!
The idea of running alternative firmware in a netgear or linksys type box is intriguing to me for one reason in particular: The idea that one could very easily add IPv6 support (via 6to4). So long as there is an IPv6 firewall that's reasonably configurable, this would make it a lot easier for me to support my folks. Instead of having to perform rather unnatural acts with the router to get to the correct machine from the outside, I could just ssh/rdp/vnc directly.
The one downside is that if your outside IPv4 address changes, then you must propagate a new prefix to the inside nodes, but even that doesn't sound like a real show stopper.
Has anyone set up something like this?
I have been trying to switch to Linux for a while, but the problem is that my wireless USB adapter (Netgear WG121) doesn't work with Linux! So I am forced to use Windows to use the internet at all. That wouldn't be so bad, except that when I am having difficulties with something in Linux, I have to go through the whole, "copy/paste error message into a text document, reboot into windows, look up problem on Google," deal. Even worse is when the solution I find doesn't work and I have to go through the process again.
There are quite an assortment of GIS tools available for Linux, too, for those of us mapping wi-fi. Check out Mapserver, GRASS, and PostGIS.
Zhrodague.net - I do projects and stuff too.
from: http://arstechnica.com/news/posts/1080251780.html
If your connection is dropping and you're not being asked to connect to another network, make sure that you have not checked the "Enable IEEE 802.1x authentication for this network" checkbox, as this can also cause problems (but was not the root cause of this issue).
---
I'm not sure what IEEE 802.1x authentication does exactly, but turning it off in XP made wireless stable. Before that I could be really close to the wireless hub and I would be randomly disconnected/reconnected every few minutes.
Do anyone here know when the support for Broadcom wireless chipsets will be included in the Linux kernel? It seems that many (at least Linksys) are moving away from Prism chipset (which I had good luck with Linux) to Broadcom chipset.
1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
Turn off the power saving options for the wifi card. do not allow windows to put the device in sleep mode and use the least power friendly option avalible for the card. these have to be changed in the driver prefs under the hardware management. i was getting the exact same problem even when sitting >10ft from the ap. when i turned off all the power save features for the card these problems went away.
-foxxz
Ok, so the Windows stuff is shaky. What's new there? At least I can get it to work without becoming an expert in wireless chipset technology. I've tried using a Proxim Symphony card with Linux with no problem. Didn't work at all with Windows. I've also tried a DLink card. Works great with windows XP-pro, but never got it to work with Linux, despite so-called TI chipset support.
:)
I've forsaken wireless for a friendly 3com 905c-TX card.
So I had a belkin card which was supposed to be based on an orionco chipset; it wasn't and it didn't work. I got a netgear, because that's what they had at comp-usa and I didn't want to waste all my freetime driving around looking for a prism2 chipset where I could be sure it was a prism2.... I got the thing, tried it, didn't work, got a copy of driverloader : done.
I'm three days into the evaulation period and I'm giving them my $20 for the software. It's too easy this way to go the free/annoying route. 'Sides, at the amount of money I end up earning/hour, spending two hours of my life to get a wireless card working it costing me more that $20.
RandomAndInteresting.comdefending the world from stupidity since 1979
I discovered that both of my Windows Laptops were dropping the connection approximately every hour and it was driving me nuts. (They are a Dell with a Broadcom 4306 (802.11g) and a Centrino Toshiba.) Even with a Linksys 802.11g WAP and an SMC 802.11b WAP I was still getting the disconnections.
Eventually after one night's worth of Windows's Eventlog data, when I forgot to switch my laptop off, I realised that there was almost precisely an hour between disconnections. An alarm bell rang in my head because on the Linksys there was an option for altering the "Group Key Renewal" for WPA. This was by default set to 3600 seconds.
One quick switch back to 128bit WEP and my connection is rock solid on both laptops.
Patriotism is the opium of the masses
M.S. wireless support is broken. XP's wireless configuration
is changed anytime your PC gets a signal from someone else's
wireless router.
It always changes the check box where you specify the source
of WAP keys. This by itself kills a wireless connection.
And, when you restate your desired configuration for sharing
keys, M.S. thought its a great idea to clear your shared
key to force you to type it in again and again!
Portions of your wireless configuration changes to conform to
the particular router it is getting a signal from.
EVEN if you set your user to "Limited" from "Administrator".
I've seen it add other routers to the "default" router table.
In pure Microsoft style, the software is beating you into
submitting to the least secure configuration since
if you turn off WAP, use DHCP and use what ever wireless router XP
detects, you can keep running.
But, if you select WAP, shared keys, static IP's you will
be constantly losing Internet access and reentering your WAP key.
Why do I feel like that Best Buy Puppet example in the begining of this story was tacked on simply to stick in a Microsoft Bash.
Since the book was about Linux, there was no real practical reason for including it. Is the book going to tell how to get around the XP problem?
No.
That's a lot of type to say simply "some wireless cards aren't supported by Linux out of the box".
It took me a long time to figure this out. I thought for a long time it was just intrinsic unreliability of 802.11b, but as I should've guessed it was Windows' fault. Having disabled Wireless Zero, my connection is now flawless on XP.
Absolutely. Wi-Fi is no where as near as reliable as good ol' ethernet, and won't be for a while. Certain cordless phoens even disrupt wi-fi. It's cute for home use, but I would *never* rely on wireless for a business use. It's just not reliable enough. I *need* my network up 100%, or my rent doesn't get paid. Wi-fi is cute, but it doesn't cut it for me. On top of that, ethernet is cheap, and very, very easy to run. At my business, we have suspended ceilings with hundreds of feet of Cat 5, and a few $20 switches.
as much as the many complaints about xp & wifi I have not had as many problems, I have found if you turn off wep (which is pretty much useless anyways) and leave only mac address protection to your wireless router the amount of lost packets/connection drops to next to nothing. Mind you it does mean someone might find out im posting at slashdot (oh the horror!) and I have to manually encrypt files that have sensative material (which you should anyways) Under Linux though as much as once the connection is started its great, getting that 1st connection is hard as hell, showing windows (in general) one point where it beats linux consistantly (and its not our exactly our fault either) hardware support.
There are, besides the SSID broadcasting issue, several other bugs in Windows XP wifi.
r am eters\General\Global]
One of them happens with WPA (which I do hope you are using, given that WEP is so easily hacked), and causes you to disconnect after a few minutes. After reconnecting there are no further problems.
This appears to be a working fix, needs a registry edit:
>> This will solve your WiFi problem! although this
>> should be considered a workaround,
>> rather than a fix. With AuthMode set to 2 it means
>> Machine authentication only.
>> Whenever a user logs in, it has no effect on the
>> connection. 802.1X authentication is
>> performed using machine credentials only.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EAPOL\Pa
"AuthMode"=dword:00000002
That will allow the machine to quickly reconnect, but it doesn't solve the actual problem. It just remedies the symptom a bit.
It is unacceptable to be disconnected, even if you are immediately reconnected. This is the situation of one of my clients.
His PC bounces while his two laptops, both on the same desk, all of which are no more than 5 feet without obstruction from the wireless router, never have a problem.
Plus his PC didn't always do that. And changing router frequency channels doesn't solve it.
Dumping the MS config and moving to a manufacturer connector is the only solution for hosed XP machines like this.
.sigs are for post^Hers.
You bought it in Japan, then?
Apparently, "AirPort" as a trademark for wireless networking was already in use by IO DATA, so Apple had to use a different name.
On the plus side, all 14 channels are allowed in Japan (13 in Europe, 11 in US/Canada, 4 in France), so my AirMac card in my iBook will work anywhere.
If your comment title says 'Re: Foo', I'm not likely to read it.
Besides user convenience, one of the benefits of wireless networks (particularly long-range wireless) is that they can compete directly with DSL, Cable modem, and landline phone service. My parents live out in the country on a hill about five miles from the nearest large town (McMinnville, OR). They have fast internet service thanks to a reasonably forward-looking ISP who set up a wireless network using radios from waverider. Unfortunately, the waverider site doesn't list prices anymore (I believe they used to sell an access point and five client radio modems for about $5000 or so, and additional radios were about $400). It uses the 902-928 mhz ISM band, so there's no FCC license required, and the line-of-sight requirements aren't as strict as 802.11. Once 802.16 (wimax) gets established, similar performing, cheaper, non-proprietary radios may become available.
This is a great way to compete with cable modem and DSL without needing to deploy much infrustructure. Any well-motivated party can set up one of these networks. It may also compel landline internet providers to offer higher throughput and better service, which is good for everyone.
-jim
Its been a while since I tried (last christmas iirc), but they seem to follow D-Link's tradition of picking a whole bunch of different chipsets & giving them all the same product number...
I think there may even be a few different 120's ( a DWL-120 and a 120g or similar) just to confuse everyone even more
Are there any USB - WiFi adaptors, that run in linux? - my family keep grumbling about the *cough*borrowed*cough* version of XP they both use - I would get internal pci cards, but my sis's pc doesnt have pci slots - its a wierd mini AST pc from several years ago. My moms is a regular pc, but its in the corner shielded by walls so I bought the usb one so i could put it in a more accessible placce
I didn't read the actual review. I fear that I am already perminantly brain damaged from the summary.
I swear it said something like "This book is not about what the title says it is about, except that three chapters actually are about that, but the rest isn't. But that stuff is related. Fuck Mocrosoft."
Oh, and somehow it lead into all that with a reference to sock puppets.
I might be wrong, but I am mortally afraid of re-reading the summary given the results of the first read.
Is the actual review any better?
-Peter
Any recommendations on the best wireless card for Linux? Both PCI and PCMCIA.
$19.95 is the cost (if not more) of a new wireless network card that is already linux supported.
Also, $14.95 is *more* than the cost of a linux supported modem. CRAZY.
Who's buying these licenses? If they were both $4.99 or less, it might makes sense.
If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
Since you are into security, perhaps you would be happy getting an STD? Security Tools Distribution, that is. That livecd will likely have any tools on it you need as well as detect your cards without any fuss.
Best of luck.
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
You think that's fun. I get a big kick out of sending print jobs :)
to my neighbor's printer over the wireless network.
I'm sure they love all the pr0n I've been printing for them, using up their toner
Microsoft disputes the notion that there's a problem with the way Windows XP works with Wi-Fi.
This may be another case of MS patches causing more harm than good... although (thankfully) I think this particular patch is "recommended" and not part of the critical updates.
A client of mine had his wireless connection drop every three or four minutes, even though the base station was under the desk at which he was working. After some research on Google, I removed the MS Hotfix for WPA (826942) and all is well.
Maybe XP tries to negotiate WPA after it's connected via WEP, and since the AP doesn't support WPA, Windows disconnects. I'm not a wireless expert so I'm guessing on that...
Note that disabling IEEE 802.1x authentication didn't help; only removing the WPA patch fixed the problem.
Solution was found here:
[wireless] Connection drops every 2-3 minutes
Thanks for the link. It's a good one. I've bookmarked it.
The page also notes another reason for not attributing it to Churchill, no one is even sure he is the original source. Common sayings, or saying of little know men, often get attributed to great men post priori in this manner.
Take "Lafayette, we are here", for instance.
A lot a Mark Twain "quotes" fall into this catagory. There's no denying he said them, but when he said them he was using what he understood his audience understood to be a common witticism from another source. When the audience, for one reason or another, perhaps just the passage of time, fail to understand that they attribute it to Twain himself.
Many of the witticisms of such great men are thus "stolen" themselves.
KFG
Yes, you got me to ssh into my home media center.
Hope That Helps. Have A Nice Day.
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
... wireless linux cards?
Repeat after me: That part of the summary was irrelevant. So is your country. So feck off. :-) ...just joking, lighten up
I think maybe some /.'ers would be able to help me out with this one. My school will soon have wireless across campus. This is a clip from their Wi-Fi access policy:
"Window's [sic] 95, 98 or earlier and Linux will not be supported."
I used to dual-boot Win98 and Fedora, but erased Win98 a few days ago and put Slack in its partition. Question is this: how are they going to stop me from using their WLAN?
Boring story short: it works, but damn is the YaST screen is nasty and watch out for non-acpi compliant (read old) mobos.
Speak truth to power.
I have to get one soon, plus build an outside antenna. My ISP is going to be running a fairly large wifi network that I am pretty sure I will be able to access, which means I can finally get broadband. The tower I will be shooting at is around 6 miles away, I can *see* that baby from my backyard. I am on a sub-beer level budget, not even close to a champagne budget, so I can only get ONE card for this project,plus cobjob the router and antenna just to get the feed. The rest of the home network will be ethernet, I got that covered already with a buncha old NICs. I guess google is my friend on this deal again. I certainly don't want driver hassles or anything, I am barely past click and drool with linux.
SuSE 9.0 was pretty much a horrible release on wireless cards as far as I can tell. My desktop system wouldn't even recognize the Netgear card under Linux until I installed the PCMCIA package through YaST. Hopefully things will improve in 9.1 (which I have yet to get ahold of) or 9.2.
...the right of the people to keep and bear arms, shall not be infringed.
thanks, I'll keep this advice in mind. Bookmarked it as well. Think I am going for a pci card though, not a pcmcia card. I am going to *try* and build my combo ethernet router and AP point out of a junker I got here. That IS a dang nice price on a laptop card though I must say.My nearest alleged computer stores are over 100 clams for a wireless router and around 50 or so for a laptop card. I don't recall the prices on a pci card. My ISP is mumbling about 200 bucks just for the outside antenna, then you need a router and phooie, I got around 50$ for the total project, so it will be a lot of junk and DIY skull sweat instead. I bet the outdoor rated ethernet cable will be the most expensive part of the whole deal. I think I am going for the flat cake pan antenna over a pringles-esque, but I haven't finished researching yet. Cake pan is cheap and can be gotten aluminum or stainless steel, which means "no rust". I DO have an old satellite tv dish, maybe I can use that thing with some hacking.
%^)
broadband, I can smell it coming.... living rural has a lot of advantages, but a few disadvantages. The good news is, building something like this increases personal knowledge base.
As long as a lot of people are complaining about XP's wireless configuration, could someone point me in the direction of the corresponding tool for Linux? I'd really like to be able to bring my laptop out of suspend in a new place and have a little dialog pop up showing me what wireless networks are around.
For added points, it should work with any wireless card and driver that is supported under Linux.
-allen
Don't you have network jacks every few feet along the walls?
Or in the floors in access panels?
That's how we do it here. We can move furniture, racks or equipment around, just replug the stuff in to whatever's closest. It's all on the same switch, so it's no big deal.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
It supports WEP (coming soon, WPA), and monitor mode. Wheeeee!!!
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
I think you guys all missed the symbolism of a puppet buying a laptop at best buy. And the saleslady says [creepy voice] "yyyoouuuuu neeeeeeeeed tththiiissssssss. ppppaaaaayyyyy myyyyy ssssssaaaalarryyyyyy."
And so he does. Ah the ingenuous ingenueeueex (I'm a french major) of puppets.
..the big computer assembly companies, who just get deals that change, so what goes inside the case changes a little bit here and there, but it's "the same make and model" when they ship them out. Like the card manufacturers might get a deal on a certain component chip one week, next week that chip runs out or they get a better deal elsewhere's, etc, and it works "good enough" without calling it a new design. Maybe anyway, I don't know. I could see where it could get fairly annoying though, and in this day and age there's no excuse for device manufacturers not coming up with linux drivers. Linux is plenty "big enough" now to have them, because linux is where the next generation of developers is coming from. I mean, I don't even see how this can be debated any longer. You think of end users/consumers, but you-as a company "you" I mean - have to think where your developers and engineers will be coming from as well if you do any sort of long range planning.
thanks
The authors of Linux Unwired have a blog at www.linuxunwired.com.
They'll be speaking and signing books at the O'Reilly Open Source Conference and at LinuxWorld.