Re: [Cooker] conf.modules, modules, modules.conf ... what's the deal?
Don Head wrote: > > > When upgrading to Mdk 7.1, and recompiling my > > kernel, Mandrake complained about > > /etc/conf.modules and mentioned that it's now > > deprecated. fine. I copied conf.modules to > > modules.conf ... exact copy, ... everything > > works fine EXCEPT my soundblaster live! value > > card (emu10k1 module). > > > > I then copied modules.conf back to conf.modules > > and everything starts up fine, even the > > soundcard, except that Mandrake complains that > > conf.modules is deprecated. What's the deal? > > And why is there also a /etc/modules file, that > > currently only has vfat as the sole module in > > it? I'd be happy to use /etc/modules.conf if > > and only if everything works! > > Rather than copying, you should try symlinks. > For situations like this, they're much more > reliable, and the preferred method. When a > change is made to one, it's also being made to > the other, because they're the same file. This > way, no matter what file is read, the contents > will always be the same. > Actually, I did use links. I sort of lied in my earlier post. I didn't literally copy anything. > ln -s /etc/conf.modules /etc/modules.conf > > (or the other way around) > > ln -s /etc/modules.conf /etc/conf.modules > Yep, I did that. Anyway, Mandrake complains when the conf.modules file (link) exists, however, the sound module is not loaded properly without it. My main question was: why are there 3 separate files in /etc related to modules? If Mandrake (newer) requires only a modules.conf file, it should be made to work for loading sound drivers too. At present, for me, (and possibly others out there) it doesn't. Gen Gen
RE: [Cooker] conf.modules, modules, modules.conf ... what's the deal?
> When upgrading to Mdk 7.1, and recompiling my > kernel, Mandrake complained about > /etc/conf.modules and mentioned that it's now > deprecated. fine. I copied conf.modules to > modules.conf ... exact copy, ... everything > works fine EXCEPT my soundblaster live! value > card (emu10k1 module). > > I then copied modules.conf back to conf.modules > and everything starts up fine, even the > soundcard, except that Mandrake complains that > conf.modules is deprecated. What's the deal? > And why is there also a /etc/modules file, that > currently only has vfat as the sole module in > it? I'd be happy to use /etc/modules.conf if > and only if everything works! Rather than copying, you should try symlinks. For situations like this, they're much more reliable, and the preferred method. When a change is made to one, it's also being made to the other, because they're the same file. This way, no matter what file is read, the contents will always be the same. ln -s /etc/conf.modules /etc/modules.conf (or the other way around) ln -s /etc/modules.conf /etc/conf.modules Don Head [[EMAIL PROTECTED]] Linux Mentor, LCA, Network+ [1 314 692-1942] Wave Technologies, Inc. [1 800 826-4640 x1942] [AIM - Don Wave][ICQ - 18804935][Yahoo - Don_Wave]
[Cooker] conf.modules, modules, modules.conf ... what's the deal?
When upgrading to Mdk 7.1, and recompiling my kernel, Mandrake complained about /etc/conf.modules and mentioned that it's now deprecated. fine. I copied conf.modules to modules.conf ... exact copy, ... everything works fine EXCEPT my soundblaster live! value card (emu10k1 module). I then copied modules.conf back to conf.modules and everything starts up fine, even the soundcard, except that Mandrake complains that conf.modules is deprecated. What's the deal? And why is there also a /etc/modules file, that currently only has vfat as the sole module in it? I'd be happy to use /etc/modules.conf if and only if everything works! I'm a bit confused, please help, thanks, Gen
