too damn true. But considering most of the linux/bsd drivers are done by reverse engineering and hacking, since the hardware companies mostly don't give a rat's ass, I am happy that they at least can produce some sort of sound / connect to my AP / connect to ethernet / display video.
if *all* hardware makers would release specs for people to write drivers for their stuff, this situation would be mucho improved.
Ever tried to install a driver in Linux? I have. I spent about 4 hours one day trying to get my wireless card working before I just said screw it. Windows? I point it at an INI file and click Next and it works. (For the record, my card _was_ supported under linux (atheros chipset), and I'm not really an idiot. I've been using BSD for a long while, so I know Unix, I just don't know Linux.) And before anyone points out that newer distros have the driver installed already, that is _not_ a solution to the problem. Drivers are still hard to install, and no matter how hard you try there will always be hardware that you don't have the drivers bundled for. Anyone who seriously thinks that Linux is _easy_ is just a fan boy.
woooa there! linux is definitely *NOT EASY*, but installing drivers is trivial. Either the device is supported, or not, and if it is supported, it *WORKS*.
I guess I know what your problem was. I had similar issues with wifi. The problem is, our beloved wifi card manufacturers have a nasty habit of producing totally different cards, but all of them have the same 'name' and sometimes even the same part number... the only thing differentiating them is some obscure shit like 'rev A', or 'v2'.
That happened to me. Did my homework, got a list of supported cards under the linux kernel, went shopping... Eventually I found a 3com '3CRWE154G72', bought it, went home, plugged it, and... the firmware would not load... i tought... wtf... Long story short, the card I bought is 'v2' and, despites having the same chipset, it has not enough memory to store the 802.11 firmware, that stuff needs to be done in the driver now, like in a winmodem. Way to go! Fortunately, that piece of shit works well with ndiswrapper (which by the way works like you seem to like : point to the.INF file and forget about it).
mwahahahah, thats the problem with this cutey-cutey 'linux distros for the braindead', when something goes wrong, braindead lusers end up staring on a black screen with garbage and a 'login:', and DUUH.
that's the reason why, when somebody asks me to recommend some distro for them to get started with linux, I recommend gentoo. That way, they are forced to LEARN how the fucking system works, and learning, at least when I last checked, is a good thing.
I am radically opposed to the 'computer as home-appliance' thing that microsoft & friends are trying to pull for a while. Computers are not nearly sophisticated enough for that paradigm to work. For now, we need people to understand how they work, and use them with responsibility. Maybe some day, when that scifi thing of computers designing new computers (and robots!) we humans can forget all about computer science and all that stuff.
which is utterly and completely fair. Nobody forces australia to 'do business' with USA, and, if they choose to do so, the USA has the right to demand whatever they want.
'he' is the guy (or gal) above who instructed a client to 'always keep windows updated, always apply the paches ASAP' (which is good), but one of the patches from redmond that the client applied broke some critical application of said client (heh, newsflash...), and 'he' had to charge the client for the support to fix it, because it was MSFT's fault, not his, yada, yada. Given that, the parent post to my mild flame said that the client had grounds to sue 'him'. Then, my 'flamebait' post.
My attitude may piss you off, but what really pisses me off is people thinking that that stuff is 'enterprise-ready software with large corporate support', when said support from MSFT is simply nonexistent, their software (bloatware) is ridden with exploitable holes, so you have to always apply their 'corporate supported patches', which turn to also be buggy and break things that worked before, yada, yada... MSFT support is no better than, say, BSD, which is as free as it gets. Actually, it is a lot worse. Try to get to 'support' some BSD servers some day, it is the easiest job in the world.
The big mistake is that corporate bozos think MSFT today is like IBM in the 'nobody gets fired for buying IBM' days... THAT was some serious (and expensive) 'corporate-backed customer support for hardware and software'.
And, to end my rant, if you read EULAs of today, 99.9% of them say that the product has ABSOLUTELY NO WARRANTY of any kind, and if your datacenter burns in flames because of it the software manufacturer doesn't give a rat's ass. Who in his right mind will pay money for something with no warranty? I'd rather use some freeware if it does the same thing, the warranty is pretty much the same.
if he gets his ass sued into oblivion, that will teach him to not touch that crap even with an 20-inch stick.
'supporting' windoze, besides making your work life a living hell, does not do anyone any good. Let them windows lusers get screwed to the point they will get sufficiently pissed of at microsoft to do something to rid themselves of that misery.
as long as there is a nerd-bitch to 'fix your windows box for some bucks', this crap will go on endlessly. I, for one, plainly refuse to do anything on any family member's computers that run windows. They have to pay some tool to clean their crap. I simply say 'i do not know windows, i don't use it, it stinks', and go back to my beer.
are you guys (you and the anonymous above) talking about 'safe mode command prompt' boot mode of windoze?
if yes, either you are messing with me (which is ok), or you have absolutely no clue about what an 'operating system that boots to cmdline' is (which is sad).
safe mode command prompt, despites being completely useless (well, I for one never seem use of 'safe mode' in any windoze version above win2k), does not even run in textmode (for you kids that never used DOS, it is that black screen with white letters that appears when the bios is doing its stuff). Not to mention that at 'safe mode command prompt' (or at 'safe mode') for that matter, there is almost nothing of the windows OS running. Can one run a windows production server in that mode? I don't think so. Not to mention it takes forever to boot in safe mode, since windows spends ages doing god knows what.
If you really think windows can be a command line OS, try this: set up a headless (no video card) windows server, which will be accessed and managed only by means of the network (telnet, ssh, whatever) or a tty console, and report back.
anyway, xen is an amazing tool to build a poor man's mainframe if you will use the OSes that have been hacked to run on it (linux, bsd, plan9...). With this new 'vt' technologies being put out by intel and amd, it will even be able to run windows (and anything that runs on a x86) without hacks.
altough it is hardly 'innovation' (ibm has done this stuff like, forever), mad pr0pz to the xen guys for bringing this to the mundane x86 world.
Slashdot Mirror
notice the quotes on 'progressives'. think ANTIFA
love it!
true that.
I tought nerds are all virgins... can a virgin be technically considered gay?
i'm more worried about the dumbing down of the mankind in general.
amen to that.
this world as it is today is a complete disgrace. idiocracy at its finest.
no and have no idea why people have pictures of wife/kids/whatever in the workplace. that's just stupid.
no you cant, unless your young self was stoned all the time.
cheers
Senior Lead Astronaut, that would impress even chicks.
yay or nay?
naaaah. you can't get fired for buying that crap.
yeah, it's much better today than the good old days when you had to have one version of the JVM for java application you used :)
meh
oooooh my precious slashkarma... must protect it...
seriously, grow up.
actually, the firewall CAN BE in the kernel. you are always free to uncheck "ip tables support" and recompile.
:)
in windows, such thing is 'unpossible'!
too damn true. But considering most of the linux/bsd drivers are done by reverse engineering and hacking, since the hardware companies mostly don't give a rat's ass, I am happy that they at least can produce some sort of sound / connect to my AP / connect to ethernet / display video.
if *all* hardware makers would release specs for people to write drivers for their stuff, this situation would be mucho improved.
Ever tried to install a driver in Linux? I have. I spent about 4 hours one day trying to get my wireless card working before I just said screw it. Windows? I point it at an INI file and click Next and it works. (For the record, my card _was_ supported under linux (atheros chipset), and I'm not really an idiot. I've been using BSD for a long while, so I know Unix, I just don't know Linux.) And before anyone points out that newer distros have the driver installed already, that is _not_ a solution to the problem. Drivers are still hard to install, and no matter how hard you try there will always be hardware that you don't have the drivers bundled for. Anyone who seriously thinks that Linux is _easy_ is just a fan boy.
.INF file and forget about it).
woooa there! linux is definitely *NOT EASY*, but installing drivers is trivial. Either the device is supported, or not, and if it is supported, it *WORKS*.
I guess I know what your problem was. I had similar issues with wifi. The problem is, our beloved wifi card manufacturers have a nasty habit of producing totally different cards, but all of them have the same 'name' and sometimes even the same part number... the only thing differentiating them is some obscure shit like 'rev A', or 'v2'.
That happened to me. Did my homework, got a list of supported cards under the linux kernel, went shopping... Eventually I found a 3com '3CRWE154G72', bought it, went home, plugged it, and... the firmware would not load... i tought... wtf... Long story short, the card I bought is 'v2' and, despites having the same chipset, it has not enough memory to store the 802.11 firmware, that stuff needs to be done in the driver now, like in a winmodem. Way to go! Fortunately, that piece of shit works well with ndiswrapper (which by the way works like you seem to like : point to the
mwahahahah, thats the problem with this cutey-cutey 'linux distros for the braindead', when something goes wrong, braindead lusers end up staring on a black screen with garbage and a 'login :', and DUUH.
that's the reason why, when somebody asks me to recommend some distro for them to get started with linux, I recommend gentoo. That way, they are forced to LEARN how the fucking system works, and learning, at least when I last checked, is a good thing.
I am radically opposed to the 'computer as home-appliance' thing that microsoft & friends are trying to pull for a while. Computers are not nearly sophisticated enough for that paradigm to work. For now, we need people to understand how they work, and use them with responsibility. Maybe some day, when that scifi thing of computers designing new computers (and robots!) we humans can forget all about computer science and all that stuff.
which is utterly and completely fair. Nobody forces australia to 'do business' with USA, and, if they choose to do so, the USA has the right to demand whatever they want.
for a completely opposed example, look at china.
nobody forces you to use windows and 'swallow shit' like you say, dude.
there are plenty alternatives out there.
'he' is the guy (or gal) above who instructed a client to 'always keep windows updated, always apply the paches ASAP' (which is good), but one of the patches from redmond that the client applied broke some critical application of said client (heh, newsflash...), and 'he' had to charge the client for the support to fix it, because it was MSFT's fault, not his, yada, yada. Given that, the parent post to my mild flame said that the client had grounds to sue 'him'. Then, my 'flamebait' post.
My attitude may piss you off, but what really pisses me off is people thinking that that stuff is 'enterprise-ready software with large corporate support', when said support from MSFT is simply nonexistent, their software (bloatware) is ridden with exploitable holes, so you have to always apply their 'corporate supported patches', which turn to also be buggy and break things that worked before, yada, yada... MSFT support is no better than, say, BSD, which is as free as it gets. Actually, it is a lot worse. Try to get to 'support' some BSD servers some day, it is the easiest job in the world.
The big mistake is that corporate bozos think MSFT today is like IBM in the 'nobody gets fired for buying IBM' days... THAT was some serious (and expensive) 'corporate-backed customer support for hardware and software'.
And, to end my rant, if you read EULAs of today, 99.9% of them say that the product has ABSOLUTELY NO WARRANTY of any kind, and if your datacenter burns in flames because of it the software manufacturer doesn't give a rat's ass. Who in his right mind will pay money for something with no warranty? I'd rather use some freeware if it does the same thing, the warranty is pretty much the same.
if he gets his ass sued into oblivion, that will teach him to not touch that crap even with an 20-inch stick.
'supporting' windoze, besides making your work life a living hell, does not do anyone any good. Let them windows lusers get screwed to the point they will get sufficiently pissed of at microsoft to do something to rid themselves of that misery.
as long as there is a nerd-bitch to 'fix your windows box for some bucks', this crap will go on endlessly. I, for one, plainly refuse to do anything on any family member's computers that run windows. They have to pay some tool to clean their crap. I simply say 'i do not know windows, i don't use it, it stinks', and go back to my beer.
are you guys (you and the anonymous above) talking about 'safe mode command prompt' boot mode of windoze?
if yes, either you are messing with me (which is ok), or you have absolutely no clue about what an 'operating system that boots to cmdline' is (which is sad).
safe mode command prompt, despites being completely useless (well, I for one never seem use of 'safe mode' in any windoze version above win2k), does not even run in textmode (for you kids that never used DOS, it is that black screen with white letters that appears when the bios is doing its stuff). Not to mention that at 'safe mode command prompt' (or at 'safe mode') for that matter, there is almost nothing of the windows OS running. Can one run a windows production server in that mode? I don't think so. Not to mention it takes forever to boot in safe mode, since windows spends ages doing god knows what.
If you really think windows can be a command line OS, try this: set up a headless (no video card) windows server, which will be accessed and managed only by means of the network (telnet, ssh, whatever) or a tty console, and report back.
hehe mods here are real pieces of work.
anyway, xen is an amazing tool to build a poor man's mainframe if you will use the OSes that have been hacked to run on it (linux, bsd, plan9...). With this new 'vt' technologies being put out by intel and amd, it will even be able to run windows (and anything that runs on a x86) without hacks.
altough it is hardly 'innovation' (ibm has done this stuff like, forever), mad pr0pz to the xen guys for bringing this to the mundane x86 world.
and it holds less (a lot less) per dollar than a hard drive.
what? a blu-ray disc (not player, the DISC) is more expensive-per-byte than a hard disk?
this cannot be right.