Hi, > Yes .. ne was in /etc/modules .. and so it tried to load it on > top of the kernel one .. > > Shouldnt make modules_install write over this file or something .. or > be made too ?? with the up to date modules to run.
I don't believe it should. There are times when I want a module available but don't necessarily want to load the module all the time. Also, the "/etc/modules" file is a Debian creation. Other distrbutions don't have a /etc/modules file, at least the last time I checked. RedHat and Slackware seem to stick modules to load in some "rc.*" file, from what I recall. Changing "make module_install" to overwrite /etc/modules is a bad idea, I think. I would prefer that the "make modules_install" behavior remain unaltered. My $0.02 :) -Ossama -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
