I am using this for reference and can successfully do a custom kernel: http://www.debian.org/doc/manuals/debian-faq/ch-kernel.en.html
I must be doing something wrong because when I try to do it again with using "Custom.2" I get this error: ----------------------------------------------------------- server:/usr/src/kernel-source-2.4.18# make-kpkg -rev Custom.2 kernel_image I note that you are using the --revision flag with the value Custom.2. However, the ./debian/changelog file exists, and has a different value Custom.1. I am confused by this discrepancy, and am halting. ------------------------------------------------------------ So I have to call it Custom.1 every time. Why can't I use different revision numbers? Furthermore....when I install the package I get this error: --------------------------------------------------------------- server:/usr/src# dpkg --install kernel-image-2.4.18_Custom.1_i386.deb (Reading database ... 15783 files and directories currently installed.) Preparing to replace kernel-image-2.4.18 Custom.1 (using kernel-image-2.4.18_Custom.1_i386.deb) ... You are attempting to install a kernel image (version 2.4.18) However, the directory /lib/modules/2.4.18 still exists. If this directory belongs to a previous kernel-image-2.4.18 package, and if you have deselected some modules, or installed standalone modules packages, this could be bad. However, if this directory exists because you are also installing some stand alone modules right now, and they got unpacked before I did, then this is pretty benign. Unfortunately, I can't tell the difference. If /lib/modules/2.4.18 belongs to a old install of kenel-image-2.4.18, this is your last chance to abort the installation of this kernel image (nothing has been changed yet). If this directory is because of stand alone modules being installed right now, or if it does belong to an older kernel-image-2.4.18 package but you know what you are doing, and if you feel that this image should be installed despite this anomaly, Please answer n to the question. Otherwise, I suggest you move /lib/modules/2.4.18 out of the way, perhaps to /lib/modules/2.4.18.old or something, and then try re-installing this image. Do you want to stop now? [Y/n] ------------------------------------------------------------------ So I stop and then move /lib/modules/2.4.18 to /lib/modules/2.4.18.old and all is well and I can continue. But I don't think I am doing this the right way. Am I not? Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
