You'll get your best information about which *chipsets* are supported for WiFi on one of the Linux on laptop sites. Just Google for Linux laptop. Once you find which chipsets are supported (native driver or ndiswrapper) try to find a PCI card that uses the same chipset. Usually, the manufacturer will offer both a PCMCIA card and a PCI card with the same chipset. Unfortunately, you may have to do a little digging to be sure.
Sorry, didn't get a chance to check for replies. I'm using the 64 bit Windows driver for the Broadcomm chipset. Someone was nice enough to post it on the Linuxant site. Not sure if they have the driver for your card there too. It *should* just be the standard 64 bit Windoze XP driver if you can find that on the SMC site.
The 32 bit driver *does not work* with a 64 bit OS (been there, tried that). If you're going to run a 64 bit version of Linux, you'll need to find a 64 bit Windoze driver for your card to make ndiswrapper work. I also got screwed by the Prism chipset crap. I bought a Netgear 54G PCMCIA card when I first got the system thinking that would let me get around having to use ndiswrapper (sounded shakey at the time). I can insert the card and it's recognized by the system but it no worky with the existing Prism driver; wrong chipset. Grrrrrrrrrrrr!
...Works like a charm for me - just be sure and have the ndiswrapper sources around to make for when you do kernel upgrades...
If you're using a rpm based distro such as Fedora, you might look into setting up Livna as a repository for yum and then just get the appropriate ndiswrapper rpm from them. The folks at Livna do a really good job of publishing a recompiled ndiswrapper rpm whenever the kernel gets updated.
I'm running ndiswrapper under Fedora Core 4 (x86_64) on a HP Pavillion laptop with a built-in Broadcomm wireless NIC. Works great.
I bought an HP zv6015 notebook last summer since my commute got suddenly longer when my company moved. I tried working with Windoze XP (Home Edition) for about two weeks before I wiped the disk and installed Linux.
It wasn't instability or anything like that. It was the absolutely gawd awful organization of the administration toolset and the, "We know better then you," unhelpfull tools once I found the right tab within a tool within a menu.
I've been happilly running Fedora Core 4 on the beasty ever since. I get a real 64 bit OS with SE-Linux (gave me a reason to learn about SE-Linux) and a built in firewall that does what I tell it to do. This means that the box is about as hard to crack as possible for running a publicly available OS. Setting it up was a piece of cake once I got beyond the Windoze specific "features" that made even installing Linux a pain and now the only maintenance I have to do is run "yum update" from time to time. I kept a copy of Windoze on a 10GB partition since that is the only way HP pushes out BIOS updates.
Are you trolling? They just had their first fatality in over 30 years of flying. It was that one in Chicago, where the plane went off the end of the runway and hit a car. The point is, there are lots of people technically qualified for just about any position. It pays to hold out for the nice ones, if you can.
Not trolling. You sort of answered your own comment though. The accident in Chicago was the first fatal accident for Southwest in 30 years. Not a bad record at all if you compare to other airlines. Also, I agree, holding out for people who fit the corporate culture of "nice" is a really good idea.
My only complaint was the original post sounded like only the competence of the ground crew mattered. I'll grant you that there are lots of non-flight related jobs at any airline that applying a criteria like nice makes sense. I'just like the idea that flight related jobs at an airline also have a criteria competence; not just "nice".
I worry that the flaw in what you are looking for is the lack of managers with the guts and talent to carry it out. It's so much easier to find an a-hole who will bully people than to find a competent manager who can successfully lead. Sadly, the more incompetent the upper management, the more likely it is that the bullying technique will be rewarded since, to appearances, lots of people working long hours and weekends seems to mean that more is being done than by well motivated people only working reasonable hours.
Fewer and fewer upper managers (C?O level) seem to understand that the same people who achieve amazing things in a forty hour week can be turned into unproductive drones working sixty hours by their favored "hard charging" overseer. Motivated people will "do what it takes" to get the job done. The same people, beaten up into working "as long as it takes," will accomplish very little. Sad.
It makes sense, doesn't it? It's a lot easier to enjoy your work environment if you don't hire jerks.:)
So then, where do we find managers? (Sorry, a few too many PHBs in my past.)
Oh, and just to actually respond to the post... I sure hope the pilots and flight crew also have some modicum of qualification for what they're doing. You'd be surprised how hard it is to be a really good stew (e.g., evacuation training, dealing with drunks or medical emergencies, etc.) let alone fly even a small plane in near perfect conditions let alone land a passenger jet at near minimums with 100+ lives riding on your ability.
Thought of the same joke. Looks like the next thing these folks should investigate is the gene that determines whether someone has a sense of humor. I see from some of the other replies that its expression seems to not be especially prevalent on/. today.
A better analogy would be killing the fly by reading aloud to it from these respective texts.
I disagree. The content was simply a means to an end not an end in itself. Replace "War and Peace" in my previous posting with "Human Action" (von Mises) and "The National Enquirer" with say "People" and I am just as happy with it. The specifics aren't the point.
In the original post, I just picked the first two current artists I could think of who wouldn't be "appreciated" by the "target audience" as well as classical music. The whole point was that they were all indistinguishable by the "target audience." Just like the fly doesn't really care which work it gets hit with; only that it gets hit. You request that the fly suddenly appreciate the artistic value of what is being use to kill it.
Probability of a default: probably greater than 25% and maybe even 50% for some bottom-dweller car dealerships.
Probability of such a calamity and someone is injured and they sue because they couldn't start their car and they get a sympathetic jury and they get a good lawyer: maybe.0000000000000000000000000000000000000001%.
The expected value for this proposition is definitely positive for using such a beasty.
You can sue over anything if you have enough money. If you don't have the money, you need to find a good lawyer who works on contingency who thinks your case will pay. Good luck with this one due to your point.
Some others have already pointed this out but, in simpler terms, I can swat a fly with either "War and Peace" or the "National Enquirer". This in no way means that I consider them to be equivalent works of literature.
Now can I get back to listening to my Barry Manilow album?
Some good classical music with maybe a little John Tesh thrown in for good measure. Just don't make me haul out the "big guns" and start playing some Celine Dion!
I keep telling the software developers I work with that they need to do more analysis of the problem they are supposed to be solving and actually come up with an intelligent design instead the crap they code. Maybe I should send them to Kansas.
The complete lack of evidence that a 2.7 kernel exists and IBM has contributed to it is just further proof that IBM has hidden not just their own contributions but everyone else's as well. The obvious solution is then to demand more "fact discovery" and sanctions against IBM for so effectively hiding this evidence.
Actually, NASA has a tendency to create planetary exploration vehicles that greatly exceed their required life-span. Specific examples are the Pioneer and Voyager space craft.
When you're sending some gizmo umpty million miles away, it's a good idea to make sure that everything "just works" or has a backup. It's kind of hard to get a repairman out there to fix something.
There's also a note for folks working in safety-related fields where regulations and immense processes dictate how to do work: Shortening cycles in such environments can better ensure people aren't killed by software failure.
Agile development methodologies are iterative. This generally means that a partial solution gets implemented now with a more complete and more correct implementation in the next iteration(s). That a defect in something like the air traffic control system or a nuclear power plant's control software will get fixed in the next iteration is probably of little consolation to the people who get killed because of it.
NO ONE claims agile development techniques should be used in these problem domains except those who have no experience in them. This is even in the description of agile software devlopment on Wikipedia (see the discussion in the section "When to use agile methods"). The reviewer is at least clueless and even possibly dangerous.
The PCMCIA subsystem has been substantially re-written. The good news is that the lame support that was there before has hopefully been fixed. The bad news is that people who had something running with the old, lame support may find out that 2.6.13 breaks it. Support in Fedora is *probably* coming but don't expect it right away:
> Date: Mon, 29 Aug 2005 01:23:22 -0400 > From: Dave Jones > Reply-To: For users of Fedora Core releases > To: For users of Fedora Core releases > Subject: Re: 2.6.13 Kernel > > On Sun, Aug 28, 2005 at 08:36:30PM -0600, David G. Miller (aka DaveAtFraud) wrote: >> The 2.6.13 version of the kernel is now available from >> http://www.kernel.org/ as well as the usual mirrors. Anyone have any >> thoughts as to plans by Fedora to move FC4 to the 2.6.13 kernel? > >'soon'. But not probably not in the next week or two. > >> I'm normally not a "new kernel junkie" but PCMCIA support gets >> significant fixes in 2.6.13. > > read as: almost complete rewrite. It needs completely different userspace, > and is almost guaranteed to break existing configurations. > We're still trying to make it work in rawhide. > > I'm not sure how this is going to play out in FC4 yet. > It may even come to the extreme of reverting chunks of it so that > the existing cardmgr style in FC4 continues to work.
Unfortunately, by the time 2.6.13 finished building on my laptop (HP Pavilion zv6015) last night, it was too late to do much besides see if it would boot (it did). Next step is get ndiswrapper working with 2.6.13 (haven't even recompiled it yet) and then see if a PCMCIA card I insert is at least recognized (it would be a nice start).
I'm currently running Fedora Core 4 (x86_64) on a HP zv6015 although I admit that it takes a little fiddling to get everything working. Really sweet though once you get a real 64 bit OS installed.
In keeping with the topic at hand, I tried Gentoo but couldn't find any display settings that worked with the flat panel and, to the best of my knowledge, they're not documented anywhere (refresh rates, etc.). When I installed Fedora I just tried some of the pre-defined HP flat panel monitors until I found one that worked. Definitely *not* worth it to scribble down the settings that work and go back to Gentoo.
An easy way to keep people from staying for more than a couple of hours is to not provide power outlets at the tables intended for laptop users. Short of somebody coming in with a fully charged spare battery or two, most laptops will chew through the battery in a couple of hours. Some will last longer but most won't.
You'll find this is true at the larger free wifi providers like Panera. You can use their wifi for only as long as your battery holds out at which point you can still sit and stare at a blank screen if you so desire.
Technical precision requirement on programming language and human language is very different, for I am (and maybe many others are) extremely lazy and just want to get things done with as little effort as possible.
Suggestion: don't quit the programming job and become a lawyer and especially not one that deals with contract law. Take a look at Groklaw to see the mess having imprecise language in some contracts causes.
The yum repositories for Fedora Development got hosed up during the delay for the release of FC4. As I understand it, the repositories for FC4testX point to the Fedora development repositories. When the release of FC4 got delayed (lawyer trouble, not technical), development stuff for FC5 started hitting these same repositories. Installing FC4 final should get you pointed to a Fedora 4 update repository.
I just ran into the same problem trying to do a re-install and finally gave up until FC4 final is out. Way to many dependency problems to try to fight through when the real thing is out now. There is some traffic on the fedora-test-list that indicates that some people are having trouble getting the final to install. I'll know more when I get home from work.
Slashdot Mirror
You'll get your best information about which *chipsets* are supported for WiFi on one of the Linux on laptop sites. Just Google for Linux laptop. Once you find which chipsets are supported (native driver or ndiswrapper) try to find a PCI card that uses the same chipset. Usually, the manufacturer will offer both a PCMCIA card and a PCI card with the same chipset. Unfortunately, you may have to do a little digging to be sure.
Sorry, didn't get a chance to check for replies. I'm using the 64 bit Windows driver for the Broadcomm chipset. Someone was nice enough to post it on the Linuxant site. Not sure if they have the driver for your card there too. It *should* just be the standard 64 bit Windoze XP driver if you can find that on the SMC site.
The 32 bit driver *does not work* with a 64 bit OS (been there, tried that). If you're going to run a 64 bit version of Linux, you'll need to find a 64 bit Windoze driver for your card to make ndiswrapper work. I also got screwed by the Prism chipset crap. I bought a Netgear 54G PCMCIA card when I first got the system thinking that would let me get around having to use ndiswrapper (sounded shakey at the time). I can insert the card and it's recognized by the system but it no worky with the existing Prism driver; wrong chipset. Grrrrrrrrrrrr!
I'm running ndiswrapper under Fedora Core 4 (x86_64) on a HP Pavillion laptop with a built-in Broadcomm wireless NIC. Works great.
Enjoy drinking a beer that is close to what Ben would have drunk.
I bought an HP zv6015 notebook last summer since my commute got suddenly longer when my company moved. I tried working with Windoze XP (Home Edition) for about two weeks before I wiped the disk and installed Linux.
It wasn't instability or anything like that. It was the absolutely gawd awful organization of the administration toolset and the, "We know better then you," unhelpfull tools once I found the right tab within a tool within a menu.
I've been happilly running Fedora Core 4 on the beasty ever since. I get a real 64 bit OS with SE-Linux (gave me a reason to learn about SE-Linux) and a built in firewall that does what I tell it to do. This means that the box is about as hard to crack as possible for running a publicly available OS. Setting it up was a piece of cake once I got beyond the Windoze specific "features" that made even installing Linux a pain and now the only maintenance I have to do is run "yum update" from time to time. I kept a copy of Windoze on a 10GB partition since that is the only way HP pushes out BIOS updates.
My only complaint was the original post sounded like only the competence of the ground crew mattered. I'll grant you that there are lots of non-flight related jobs at any airline that applying a criteria like nice makes sense. I'just like the idea that flight related jobs at an airline also have a criteria competence; not just "nice".
No mod points so I'll just say, "Superb."
I worry that the flaw in what you are looking for is the lack of managers with the guts and talent to carry it out. It's so much easier to find an a-hole who will bully people than to find a competent manager who can successfully lead. Sadly, the more incompetent the upper management, the more likely it is that the bullying technique will be rewarded since, to appearances, lots of people working long hours and weekends seems to mean that more is being done than by well motivated people only working reasonable hours.
Fewer and fewer upper managers (C?O level) seem to understand that the same people who achieve amazing things in a forty hour week can be turned into unproductive drones working sixty hours by their favored "hard charging" overseer. Motivated people will "do what it takes" to get the job done. The same people, beaten up into working "as long as it takes," will accomplish very little. Sad.
Oh, and just to actually respond to the post... I sure hope the pilots and flight crew also have some modicum of qualification for what they're doing. You'd be surprised how hard it is to be a really good stew (e.g., evacuation training, dealing with drunks or medical emergencies, etc.) let alone fly even a small plane in near perfect conditions let alone land a passenger jet at near minimums with 100+ lives riding on your ability.
Thought of the same joke. Looks like the next thing these folks should investigate is the gene that determines whether someone has a sense of humor. I see from some of the other replies that its expression seems to not be especially prevalent on /. today.
Cheers,
Dave
In the original post, I just picked the first two current artists I could think of who wouldn't be "appreciated" by the "target audience" as well as classical music. The whole point was that they were all indistinguishable by the "target audience." Just like the fly doesn't really care which work it gets hit with; only that it gets hit. You request that the fly suddenly appreciate the artistic value of what is being use to kill it.
Probability of a default: probably greater than 25% and maybe even 50% for some bottom-dweller car dealerships.
.0000000000000000000000000000000000000001%.
Probability of such a calamity and someone is injured and they sue because they couldn't start their car and they get a sympathetic jury and they get a good lawyer: maybe
The expected value for this proposition is definitely positive for using such a beasty.
You can sue over anything if you have enough money. If you don't have the money, you need to find a good lawyer who works on contingency who thinks your case will pay. Good luck with this one due to your point.
Some others have already pointed this out but, in simpler terms, I can swat a fly with either "War and Peace" or the "National Enquirer". This in no way means that I consider them to be equivalent works of literature.
Now can I get back to listening to my Barry Manilow album?
Some good classical music with maybe a little John Tesh thrown in for good measure. Just don't make me haul out the "big guns" and start playing some Celine Dion!
Yes, the original paper has goto as two words.
I keep telling the software developers I work with that they need to do more analysis of the problem they are supposed to be solving and actually come up with an intelligent design instead the crap they code. Maybe I should send them to Kansas.
The complete lack of evidence that a 2.7 kernel exists and IBM has contributed to it is just further proof that IBM has hidden not just their own contributions but everyone else's as well. The obvious solution is then to demand more "fact discovery" and sanctions against IBM for so effectively hiding this evidence.
So send both mounties over in a canoe with a swarm of mosquitoes for escort to teach us a lesson.
Now I understand why the Quebecois want out. I used to think they were the nut cases.
Actually, NASA has a tendency to create planetary exploration vehicles that greatly exceed their required life-span. Specific examples are the Pioneer and Voyager space craft.
When you're sending some gizmo umpty million miles away, it's a good idea to make sure that everything "just works" or has a backup. It's kind of hard to get a repairman out there to fix something.
NO ONE claims agile development techniques should be used in these problem domains except those who have no experience in them. This is even in the description of agile software devlopment on Wikipedia (see the discussion in the section "When to use agile methods"). The reviewer is at least clueless and even possibly dangerous.
The PCMCIA subsystem has been substantially re-written. The good news is that the lame support that was there before has hopefully been fixed. The bad news is that people who had something running with the old, lame support may find out that 2.6.13 breaks it. Support in Fedora is *probably* coming but don't expect it right away:
> Date: Mon, 29 Aug 2005 01:23:22 -0400
> From: Dave Jones
> Reply-To: For users of Fedora Core releases
> To: For users of Fedora Core releases
> Subject: Re: 2.6.13 Kernel
>
> On Sun, Aug 28, 2005 at 08:36:30PM -0600, David G. Miller (aka DaveAtFraud)
wrote:
>> The 2.6.13 version of the kernel is now available from
>> http://www.kernel.org/ as well as the usual mirrors. Anyone have any
>> thoughts as to plans by Fedora to move FC4 to the 2.6.13 kernel?
>
>'soon'. But not probably not in the next week or two.
>
>> I'm normally not a "new kernel junkie" but PCMCIA support gets
>> significant fixes in 2.6.13.
>
> read as: almost complete rewrite. It needs completely different userspace,
> and is almost guaranteed to break existing configurations.
> We're still trying to make it work in rawhide.
>
> I'm not sure how this is going to play out in FC4 yet.
> It may even come to the extreme of reverting chunks of it so that
> the existing cardmgr style in FC4 continues to work.
Unfortunately, by the time 2.6.13 finished building on my laptop (HP Pavilion zv6015) last night, it was too late to do much besides see if it would boot (it did). Next step is get ndiswrapper working with 2.6.13 (haven't even recompiled it yet) and then see if a PCMCIA card I insert is at least recognized (it would be a nice start).
Said parking lot would also be self-lighting (at least for several years).
Time to burn some mod points. I wonder how low the liberal whiners here can mod me down.
S I G H.
I'm currently running Fedora Core 4 (x86_64) on a HP zv6015 although I admit that it takes a little fiddling to get everything working. Really sweet though once you get a real 64 bit OS installed.
In keeping with the topic at hand, I tried Gentoo but couldn't find any display settings that worked with the flat panel and, to the best of my knowledge, they're not documented anywhere (refresh rates, etc.). When I installed Fedora I just tried some of the pre-defined HP flat panel monitors until I found one that worked. Definitely *not* worth it to scribble down the settings that work and go back to Gentoo.
An easy way to keep people from staying for more than a couple of hours is to not provide power outlets at the tables intended for laptop users. Short of somebody coming in with a fully charged spare battery or two, most laptops will chew through the battery in a couple of hours. Some will last longer but most won't.
You'll find this is true at the larger free wifi providers like Panera. You can use their wifi for only as long as your battery holds out at which point you can still sit and stare at a blank screen if you so desire.
The yum repositories for Fedora Development got hosed up during the delay for the release of FC4. As I understand it, the repositories for FC4testX point to the Fedora development repositories. When the release of FC4 got delayed (lawyer trouble, not technical), development stuff for FC5 started hitting these same repositories. Installing FC4 final should get you pointed to a Fedora 4 update repository.
I just ran into the same problem trying to do a re-install and finally gave up until FC4 final is out. Way to many dependency problems to try to fight through when the real thing is out now. There is some traffic on the fedora-test-list that indicates that some people are having trouble getting the final to install. I'll know more when I get home from work.