On 6 Apr 2000, Chmouel Boudjnah wrote:
> David Walluck <[EMAIL PROTECTED]> writes:
>
> > 3.) modules.dep is not created when it should, and this casuing all sorts
> > of problems upon the first boot into the new kernel.
>
> are you sure ? this may be related to shm stuff.
Yes, this is what I wrote about before. Please do depmod -a
kernel-%version} in %post, otherwise we have no modules.dep on first
boot. Also, this could detect problems like the "pre" problem I also
mentioned.
> > 5.) modules.conf has chnaged greatly, and there should be some script (i.e
> > installkernel, that does versioning for modules.conf).
>
> i don't understand.
I mean how there is symlinks for vmlinuz and current System.map in /boot,
that there could also be symlinks for modules.conf.
>
> > 6.) modules.conf shouldn't still be called conf.modules. There's a patch
> > to get rid of the warnings but it still b*tches about symlinks and
> > modules.dep being older. But really it's bad because most programs change
> > conf.modules, and if you're using modules.conf nothing will happen.
>
> for next version, jumping to /etc/modules.conf is more than a small
> hack (a /lot/ program do grep/sed/awk/perl on /etc/conf.modules)
Maybe this is the same anwser as for 5. The new devfs in kernel 2.3.99
changed modules.conf completely, and the 2.2.xx one isn't really
compatible, so it makes it hard to boot between versions if you have a lot
of modules.
