It also doesn't allow RPC2 drives using RPC1, which is an evasive way of saying "drives with hacked region-free firmware."
Take it from me, a very large percentage of the popular drives have this firmware available, and a significant number of users use it. By locking them out, they've just pissed off the end user, and if the end user is a Joe Durr who doesn't know what RPC1 or RPC2 are, they'll start bitching at their nerdy associate for their drive being broken...and, more than likely, just shove it and buy a new drive rather than listening to words like "reflash."
Of course, my personally trained users aren't that stupid...but I know a lot that are.
For Windows machines, pre-SP2, the wireless driver API sucked. Utterly. Windows had no idea what the fuck wireless cards were or why it should care that a card was wireless, for the most part. It just treated it as an ordinary NIC with weird properties, which meant that the companies all got to giggle and add proprietary hooks for shit like signal strength and anything besides basic ad-hoc/infrastructure modes...which is where we get the incredibly bloated drivers from. Similarly, all-in-one printers do the same thing, because they want to have the properties of a scanner, printer, and god knows what else, so they basically load one driver and then have some shitty stub of a driver that pipes everything to the other one in proprietary hooks (my mother received a Lexmark all in one for free, and you can install a plain scanner driver fine, but if you want to use the printer, you have to install their shitty bloated app which feeds it into the scanner driver...not joking.)
The problem, of course, is that you can't install the drivers in question without the shitty application bloat, because the drivers often install the bloated apps along with them, or don't function properly without them (I turn to my above printer example).
Wireless networking drivers are a mess. Linux and Windows are both scrambling to fix it, and Linux has a decent attempt at a standard 802.11 stack, though it still has bugs [last I checked, no Master mode support, and it breaks most old-school wireless drivers if you enable it]. Windows is probably trying, but in attempting to avoid driver breakage, they're stuck with those old drivers forever.
Why the fuck would dd care about the TOC? It just dumps until the if= spits out EOF. I suppose if it has physical defects, sure, but that's an easy workaround.
No, because theirs actually does something useful, whereas Hotmail's has failed to catch a lot of the viruses people randomly send me while simultaneously denying people legitimate attachments because they fit some extension that Hotmail blocks.
Bull. The Ralink chipset has nice Linux drivers (the old ones were derived from the same source base as the Windows drivers, but the rewrite is so much better - and well supported), as well as any Atheros card. Prism cards are well-supported, and rtl8180 cards will work (when you figure out what order you do crap in.:) )
Centrino you mentioned already has excellent Linux support.
The ACX1xx, as well as a few other obscure chipsets, have Linux support, but it's spotty.
The moral is, there are chipsets with good support, even though there are also some with really bad support.:)
I find your example particularly offensive, as Linux can use the Windows drivers for some of those.:)
I find your example particularly offensive because your analogy is flawed. The Windows wireless drivers are hacks, and the API only supports the most basic functionality - that's why most of the wireless drivers you get come with those weird-ass nasty interfaces - to hide the fact that Windows doesn't have a standard way to use that functionality.
At least under Linux we have a standard for doing those things.
Slashdot Mirror
It is possible, though annoying, to disable HTTP functionality in Konq. And you can use other file browsers in KDE. :)
It also doesn't allow RPC2 drives using RPC1, which is an evasive way of saying "drives with hacked region-free firmware."
Take it from me, a very large percentage of the popular drives have this firmware available, and a significant number of users use it. By locking them out, they've just pissed off the end user, and if the end user is a Joe Durr who doesn't know what RPC1 or RPC2 are, they'll start bitching at their nerdy associate for their drive being broken...and, more than likely, just shove it and buy a new drive rather than listening to words like "reflash."
Of course, my personally trained users aren't that stupid...but I know a lot that are.
It's either intentionally making a joke or is trying to see if people with mod points are bored.
Either way, the Informative mod is wrong.
The contact of the "Anonymous Coward" who submitted the story is workshop@santastars.com.
Hmm...
For Windows machines, pre-SP2, the wireless driver API sucked. Utterly. Windows had no idea what the fuck wireless cards were or why it should care that a card was wireless, for the most part. It just treated it as an ordinary NIC with weird properties, which meant that the companies all got to giggle and add proprietary hooks for shit like signal strength and anything besides basic ad-hoc/infrastructure modes...which is where we get the incredibly bloated drivers from. Similarly, all-in-one printers do the same thing, because they want to have the properties of a scanner, printer, and god knows what else, so they basically load one driver and then have some shitty stub of a driver that pipes everything to the other one in proprietary hooks (my mother received a Lexmark all in one for free, and you can install a plain scanner driver fine, but if you want to use the printer, you have to install their shitty bloated app which feeds it into the scanner driver...not joking.)
The problem, of course, is that you can't install the drivers in question without the shitty application bloat, because the drivers often install the bloated apps along with them, or don't function properly without them (I turn to my above printer example).
Wireless networking drivers are a mess. Linux and Windows are both scrambling to fix it, and Linux has a decent attempt at a standard 802.11 stack, though it still has bugs [last I checked, no Master mode support, and it breaks most old-school wireless drivers if you enable it]. Windows is probably trying, but in attempting to avoid driver breakage, they're stuck with those old drivers forever.
Oops.
So they're copying something from NT 3.51 and marking it as a new feature.
It's still a copycat.
Why the fuck would dd care about the TOC? It just dumps until the if= spits out EOF. I suppose if it has physical defects, sure, but that's an easy workaround.
I suggest that you should probably use the noerror and possibly notrunc options to dd, and it'll copy fine.
It's been spammed before, but I'll say it again.
CmdrTaco has always said this is his blog, we just choose to read it. He rarely makes personal posts any more, but such it remains, according to him.
Don't like it, so be it.
No, an extra X chromosome would be useful.
It would motivate those of us with XXY to go into game design instead of, say, anything where you have to be comfortable with other people.
...considering it's not posted to Index. :)
So embed it in an encrypted ZIP inside of an encrypted RAR inside of a 7zip archive. :)
No, because theirs actually does something useful, whereas Hotmail's has failed to catch a lot of the viruses people randomly send me while simultaneously denying people legitimate attachments because they fit some extension that Hotmail blocks.
It's faster than IE in some cases, and you don't have to call your relative every few days to clean up your system.
Firefox 1.5 RC3, MPlayer plugin 3.15, works fine here.
Any more questions?
Most of the other tips are good, but nobody's mentioned CCleaner yet. That is one awesome app for cleaning out old cruft.
I knew I forgot something - yeah, the new Prism54 cards are bad under Linux. The old ones, would that you can find one, are awesome, though.
Granted. Here is a list of Ralink cards.
Bull. The Ralink chipset has nice Linux drivers (the old ones were derived from the same source base as the Windows drivers, but the rewrite is so much better - and well supported), as well as any Atheros card. Prism cards are well-supported, and rtl8180 cards will work (when you figure out what order you do crap in. :) )
:)
Centrino you mentioned already has excellent Linux support.
The ACX1xx, as well as a few other obscure chipsets, have Linux support, but it's spotty.
The moral is, there are chipsets with good support, even though there are also some with really bad support.
Nobody tell Scott Kurtz! We'll never hear the end of it!
When the playground is built for someone one-fifth your size, yes one is.
A Katamari-based playground would be awesome. I'd totally play on it, though I think I might be too old for it. :)
Though some of the parts are missing, a lot of DX is working in WINE. :)
I find your example particularly offensive, as Linux can use the Windows drivers for some of those. :)
I find your example particularly offensive because your analogy is flawed. The Windows wireless drivers are hacks, and the API only supports the most basic functionality - that's why most of the wireless drivers you get come with those weird-ass nasty interfaces - to hide the fact that Windows doesn't have a standard way to use that functionality.
At least under Linux we have a standard for doing those things.
I'll do you one better - I loathe the smell, and gives me horrible heaadaches if I smell too much of it.