Comment 36 for bug 213081

Stefan Bader wrote:
> no you should not see more than two, all the other binary packages mentionen on that page are just udeb packages (which I personally have never used, they are just automatically created). You will just see a new kernel (and maybe the kerneloops package).

 > One thing, as you said you use a production system. You need to
enable the hardy-proposed option in the sources so you get the matching
linux-ubuntu-modules (and maybe linux-restricted-modules and
linux-backports-modules, depending on your setup) because this is a
kernel with a different ABI version -21 (instead of the current -19).

I added your ppa to my sources.list, and also added hardy-proposed to
collect any pre-requisites.

I can see your package kernel-image-2.6.24-21-generic-di (version
2.6.24.21.40smb) is available for upgrade, but am surprised at several
things...

1. It has NO dependencies.

2. The description says "This package contains the Linux kernel image
for the Debian installer boot images. It does _not_ provide a usable
kernel for your full Debian system"

3. package linux-image-generic shows a latest version of 2.6.24.21.23
(hardy-proposed) - not your one.

I am nervous about marking all available upgrades, because I am will
pick up a 23 changes that are not yet released for production use.

Which packages should I install to prepare my system to use your
kernel-image?

Can I just install your image package, or will I need to run initramfs
manually?

> There is an alternate way if you feel more comfortable with that. You can follow the link below and download the kernel image directly.
> http://ppa.launchpad.net/stefan-bader-canonical/ubuntu/pool/main/l/linux/

I went there, but it has a load of stuff available... nothing there
seemed to answer my questions above. I would prefer to use the tools I
am familiar with - synaptic or update-manager.

Sorry to ask for so much help and advice, but you are taking me into new
territory. I'm an expert with network protocols, not linux kernels or
debian package management. If you had to wait for me to research all
this "new" stuff, you'd wait for ever before I could run a simple trace
and confirm the tcp/ip protocol fix!

Once I have your kernel booted, I only need about 10 minutes to do my
stuff. But then I need to restore my system to its production state and
get back to (paid) work. I'll continue using the net.ipv4.tcp_frto
bypass until an official fix becomes available.

Regards,

Brian