Samstag, 5. Januar 2008 Tom Patton:
I do not see this as a major issue, or one that fuels the MS war.
People who cannot fiddle around in root shells will definitely get the impression of a major issue going down when their supported and functional tv card stops working after an online update.
Is it really that hard to understand what advice like "Oh, just open a terminal, become root, edit out some lines from /etc/modprobe.d/blacklist and reload a kernel module" does to ordinary people?
I'm reasonably certain that the root cause will eventually be resolved, and THEY will remove the black-list sheriff ANYWAY.
They will probably not because there are loads of devices that need to be blacklisted, potentially.
Imagine the odds of even BEING ABLE TO WORK_AROUND in a MS system!!! Good luck with THAT chore, sir. I'm sure this WOULD have been a windoz show-stopper, with the only hope to wait 6 months for an update!!! Give me SuSE ANY DAY!
3 months and counting ... https://bugzilla.novell.com/show_bug.cgi?id=330109
The ubiquitous notion of linux geeks that their distributions are superior to any other commercial OS would gain some decent weight through serious bug-squashing. Mindlessly repeating it over and over does not make it any truer. It just makes us a laughing stock really.
Wolfgang You missed my point, I think, in that a usable system is easily restored by slight manual intervention. And an even-better suggestion was already posted in the bug. However, I have now added a new comment to
From what I see, I think this only occurred when choosing "unknown card", and I suspect the majority of tv cards have been working fine all along. Otherwise, there would have been much more traffic here in the forum. This particular thread is the only one I've noticed about the issue, and my comment today to the bug was only the 6th vote in its
On Sat, 2008-01-05 at 21:20 +0100, Wolfgang Woehl wrote: the bug, and perhaps that will bring it back into focus. lifetime... As for black-listing, that certainly seems appropriate as a protective measure, and was documented. In this instance, it seems to be benign, but I can imagine other situations and devices which could cause serious problems. Whatever.... Tom in NM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org