> >But not the kernel. My kernel is still at > 2.2.17, even though > >the only kernels on the debian mirrors are > various 2.2.19-based > >things. > > > >Why?
Because. Do you really want to replace a custom built kernel with a stock kernel? In order to allow things like that, Kernels aren't versioned so that upgrades won't occur to them. It used to be the other way, and it didn't work well. You had to 'epoch' number the kernel so it wouldn't upgrade automatically. > I would suspect that packages that have version > numbers in the base name, > like lsof-2.2 (or lsof-2.0.36) would require > this kind of manual selection. > Several scripting language packages appear to > use this theme as well. Bingo. One of the primary Debian rules: do it the right way, even if it doesn't seem to make as much sense at first. Do you really want the latest version of ProgramX, if the syntax has changed and some of your existing code will break? No. Seth __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/
