I decided I likely had answered my own question. Copied the modules directory and modules.conf files, then let apt install over my image (after which the upgrade finished normally). I then immediately reinstalled the custom over that. Recopied the old files back and was done.
Kenward On Mon, Sep 25, 2000 at 09:08:39PM -0400, Joey Tsai wrote: > I had the same problem. I just did a make-kpkg with "-revision 2:Custom.2" > (my > previous custom kernel was "Custom.1") and installed the new custom kernel. > I > don't know if this is the "right" or "best" way, but apt is cool now. > > // joey tsai > > > :: Kenward Vaughan :: > > I'm in the middle of a woody upgrade, and discovered that the latest > > greatest > > kernel image has been DL'd and is attemping to overwrite my custom 2.2.17 ... -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! --
