Wow... I've been running a nice, solid, stable pair of 2.0.34 and 2.0.36 systems. Decide to upgrade to 2.2.0 kernel. Download, see warnings on versions of required packages. Test versions, lots out of date. Change dselect from dists/stable to dists/unstable, <barf>. Change to dists/frozen (yeah, I forgot about the move from unstable to frozen!), dselect upgrades everything except nfs-server (only to b37 instead of the listed b40), procinfo (can't find at all) and pcmcia-cs (older than recommended 3.0.7). Find procinfo via FTP, try to install - it barfs. Can't be important. Can't find pcmcia-cs; don't want pcmcia - can't be important. Can't find a newer nfs - it's a server package, this is a workstation, can't be important... Everything reboots fine. Still uneasy about upgrade, but what the heck - what can go wrong? :-)
Follow installation instructions on tty1, read instructions on tty2, kernel-howto open on another PC. Make runs fine, no warnings, all is happy during compile. Reboot gives module errors. Rename /etc/modules, all looks and works. Question is, what did I miss or do wrong? Nothing broke or died... Nothing barfed (except for my misguided attempt to upgrade from hamm to potato). I thought this stuff was supposed to be difficult - that's what all these Windows weenies I work with tell me :-) </humorous interlude> (BTW, same procedure worked on my home PC - the 2.0.36 system. I think all the development time and -pre releases did some good here. The people I tell about it shake heads in disbelief... Of course, it's tough to not brag that it went so smoothly because of my incredible kernel hacking skill <g>...)
