Hi! I've written a short description of steps I follow to manage kernel updates. It includes some code for automatic packing and naming of initram-images suiting names given to the kernels by doing "make install" in the kernel directory. Feedback appreciated.

Olek: I don't blame Noscript for doing its job - protecting me from possible exploits - It's only one stage of my system security. The problem I have is with blogspot in general as I've encountered attack code due to some links to pages posted there. They were cleaned up by them pretty quickly but the damage was already done as far as I'm concerned. Another factor is that the site is useless to me from work because the IT dept has things locked down pretty tightly and they block blogspot for what ever reason. In other words, all I get at home is a blank page and from work I can't even access the site.

So unless you're method runs to more then a couple of hundred lines of code, there's no reason you can't post it to the forums. If an Admin says otherwise, they'll tell you and give you suggestions that don't tend to break on Linux systems that maynot have the features installed that Blogspot depends on (like the cookies blogspot wants to set just to view things. Sorry google but I don't need your features that badly.

I'd say that was pretty painless and provides the code to the rest of us who dislike/can't allow/access blogspot. Now all I have to do is review how you're doing it and see if it suits my needs.

On the section about making a new kernel and updating grub, both of those are redundent to the discussion of how you've automated the creation of the initram, which is why I didn't include them. Another is I tend to use the vanilla-sources and dislike grub/grub2 preferring lilo instead - and no, I wont get into a debate as that's an entirely different topic and deserves its own thread.