So, I got with the program and used kernel-pkg to build my local copy of 2.2.17. I followed the directions and named it with an extension of "custom.1.0".
Now I do an "apt-get -s upgrade" (for woody) to see what's what, and it wants to install and configure the Debian kernel-image-2.2.17 package over mine. I thought the above name would prevent this. Is this an example of the ever-mysterious "epoch"? Brr, I got a shiver just typing it. So. How can I convince apt-get to cleave only unto my customized kernel package, forever forsaking all others, as long as we both shall live? Is there any way other than rebuilding and reinstalling my kernel package with an even _higher_ epoch, in a veritable arms race of package version numbering? -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> Network Management Development "Please remain calm...I may be mad, but I am a professional." --Mad Scientist ------------------------------------------------------------------------------- These are my opinions---Nortel Networks takes no responsibility for them.
