modules directories
I was just playing a little bit with the 2.1.5 kernel (seems to run pretty
well). However, the modversions have changed. This is no problem with the
kernel modules, but obviuosly ibcs, ntfs and elks don't run anymore.
But I don't want to replace them since I keep a stable kernel on the
machine, too. So I thought about copying the modules into the kernel
specific subtree (e.g. 2.0.23/fs instead of fs) but I don't think this is a
wise idea, since I remove the subtree once a new version comes out and tend
to forget to move them out before. Since this modules won't change as much
with new 2.0 releases I thought of adding a 2.0 resp. 2.1 subtree for third
party modules.
All that has to be added is the following entry (or a similar one) in
/etc/conf.modules:
path[fs]=/lib/modules/`uname -r|cut -f1,2 -d.`/fs
path[misc]=/lib/modules/`uname -r|cut -f1,2 -d.`/misc
path[net]=/lib/modules/`uname -r|cut -f1,2 -d.`/net
path[scsi]=/lib/modules/`uname -r|cut -f1,2 -d.`/scsi
path[block]=/lib/modules/`uname -r|cut -f1,2 -d.`/block
path[cdrom]=/lib/modules/`uname -r|cut -f1,2 -d.`/cdrom
path[ipv4]=/lib/modules/`uname -r|cut -f1,2 -d.`/ipv4
The packages with kernel modules then could install into 2.0/misc resp.
2.0/fs. If we start providing a 2.1.X version later that won't break
anything.
Comments anyone?
Michael
--
Michael Meskes | _____ ________ __ ____
meskes@informatik.rwth-aachen.de | / ___// ____/ // / / __ \___ __________
meskes@sanet.de | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/
meskes@debian.org | ___/ / __/ /__ __/\__, / __/ / (__ )
Use Debian GNU/Linux! | /____/_/ /_/ /____/\___/_/ /____/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: