Wolfgang Pfeiffer wrote:
Hi All

After recompiling the same kernel-version (2.6 flavor) I want to make
sure that the previously installed modules of this same kernel-version
in /lib/modules/<some-kernel-version>/ will not be overwritten by the
newly compiled same kernel revision when installing it. Is this
possible?


try:

$less /usr/share/doc/kernel-package/README.gz

It's a detailled explanation of how make-kpkg works (although my worthless opinion is that if you are only compiling a kernel for one machine there is not too much point to creating a debian package)

An extract which I think answers your question:

| If I may digress to talk about "--append-to-version",
| "--append-to-version=bla" affects the name of the Debian package
| itself, and also appends the append-to-version text to the kernel name
| AND to the modules directory name when dpkg installs the kernel, so
| this kernel will have its own set of modules, separate from the
| modules used by the default kernel with the same version.

Anyway if you are paranoid you could always rename
        /lib/modules/<version>
to:     /lib/moduels/<version>.old
before installing your kernel package!

HTH

--
Arnaud


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to