also sprach Shaya Potter <spotter@opus.cs.columbia.edu> [2001.12.28.0828 +0100]: > tainting doesn't prevent any modules from loading. If your modules are > not loading, its something else. Modules that "taint" the kernel, but > shouldn't (like pcmcia-cs) are buggy and should be fixed. you are right. it's related to my other post on /lib confusion... i still had the older (incompatible) pcmcia-cs modules in /lib/modules/2.4.17/pcmcia, since pcmcia-cs decided to install in /lib/modules/2.4.17+fishbowl/pcmcia (i am using flavours to indicate machine names). this is another issue, but the tainted modules "problem" is solved... thanks. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck echo Prpv a\'rfg cnf har cvcr | tr Pacfghnrvp Cnpstuaeic
Attachment:
pgps4EbSpGNWR.pgp
Description: PGP signature