As a system administrator, I have some relatively strong opinions on howLinux distributions and packaging systems should handle kernel updates.Since I have just gone through the experience of yet another mass kernelupdate of our servers, I feel like writing them up:

• you should be able to have multiple kernels installed at once.
• it should be easy to tell which package's kernel you are running,and thus whether or not you are running the most current kernel.
• installing a kernel update should never overwrite an existingkernel image;

One of the things that I hate about typical debuggers is that they wantme to hold their hand all the time. Okay, this is not entirely fair;they default to having me hold their hand, and generally don't do areally good job of supporting hands-off operation.

This is not really their fault, because debuggers have a differentview of how they're going to be used than I do. A classical debugger(like gdb ) expects to be used by people who are carefully narrowing

Suppose that you have accidentally published a blog entry that you really didn't want to and now want to retract, unpublish, disappear, or the synonym ofyour choice the entry. You could just delete the entry, but thishas a problem: your syndication feeds (RSS, Atom, et al).

Specifically, removing an entry from your blog and thus your feeddoesn't remove it for people who've already fetched a version of yourfeed that included the entry. Feed readers keep their own