Tainted modules and possible boot problems!

Mike McCarthy wrote:
> SuSE sets the "taint" flag all over the place. These are not in the default
> kernel distribution. The only reason they are there is to give the Novell
> support desk an "out" to deny you support if they see that a "taint" flag
> is present. I agree that it is a bad thing.

I only use the official kernel in any SuSE distribution to perform the installation and as a
last-chance backup in case I bollux my mainline kernel. Tainting GPL code is another reason to use
my own kernel. The main reason was because I tend to be a couple of distributions behind (I'm now
running SuSE 10.0) and the SuSE official kernel is a little long in the tooth for me. In addition, I
am the kernel maintainer of the bcm43xx driver, which wasn't put into mainline until 2.6.17, and it
wouldn't do to be running a 2.6.13 kernel.

Larry