""Well, sometimes there truly is little choice. ""
If you have no choice, then you have no choice.
What I have a problem with is people, posing as experts, recommending to new users to
blacklist open source drivers to get NDIS wrapper working.
This is when I have the same exact devices and they are working perfectly well with no NDIS
wrapper!
What they should do instead is figure out what went wrong, file a bug report, and get a
working driver and try to get that stuff back into the distro, or at least provide a download,
so that they are actually helping the people they are claiming to help instead of advising
users to try to shoehorn Windows drivers into their kernel.
Posted Mar 5, 2008 22:51 UTC (Wed) by proski (subscriber, #104)
[Link]
Users who believe such "experts" are usually not good at bug reporting. They would forget to provide important information about their systems, they would be loaded with incorrect assumptions taken from "experts" in "helpful" forums, they would fail to read the documentation, they would trust obsolete posts they find on Google more than the current documentation. And even if they manage report a bug more or less correctly, it would be either a known issue, or something already fixed in the git repository and being on its way to the distros. But it's unlikely such users would bother testing the fix.
In any case, it's unfair to advocate blocking free software just because it has some clueless proponents. Just because, say, KDE has some idiotic fans, it doesn't mean that developers of other software (e.g. gcc, libc) should be actively looking for ways to prevent KDE from compiling or working properly, and it particular blacklist KDE modules by name, as it was done to ndiswrapper.
NDISwrapper dodges another bullet
Posted Mar 6, 2008 5:45 UTC (Thu) by allesfresser (subscriber, #216)
[Link]
What I found really annoying was people (yes, on the Ubuntu forums) who told a user, as you
said, to blacklist the free driver in favor of ndiswrapper. However, the system in question
happened to be using a *PowerPC processor*. Obviously this will not do the user much good, to
load a Windows driver in this case...