Originally Posted by the trooper
How so?,I run a custom kernel kernel myself as do many others who run Debian.
As did I for a number of years. But going from etch to lenny, the config for my custom kernel that I've used for quite some time did not result in a bootable kernel via grub 2. Even taking the /boot/config from the debian kernel and modifying it to my minimalistic needs resulted in an unbootable kernel. Even though I was using the same kernel and same config from etch that I had used for months. Note: not the kpkg-make or whatever the package variant of a custom install. Note: 184.108.40.206 because I've got one of those old video cards (laptop) that ATI's proprietary drivers stopped working on since their 9.3 driver. Note: I generally only enable the features that I use, even though there is hardware with drivers that I don't use.
Since upgrading to Debian Lenny I've only been able to run Distro kernels. Simply because I cannot seem to boot any custom kernel that I can come up with. And I've been running and configuring custom kernels for years. Not that it matters that much on my current very dated hardware where the stock kernel does most of what I need it to do. (except low latency for audio or compiled specifically for my CPU).
I'll have to look into that.
As far as packages. In past versions I've tried upgrading from a minimal install to testing and add packages from there. And certain rather common packages were no longer available like Evolution, Open Office, and other things when I went that route. At which point I either had to start from square one (being on dialup at the time) or just do the next upgrade to sid to obtain access to what I considered basic packages back then. I opted for sid, since I couldn't even get the testing versions of things from packages.debian.org and other headaches. Of course sid had about a 10MB average of updates per day at that time. Which is an hour commitment PER DAY over dialup to stay current. And if some things were in flux like open office or kde, eternal bandwidth never current loop from hell.
Fortunately I'm now on quasi-broadband (2 megs) and updating just the list of packages isn't a half hour commitment or longer anymore.