Re: Bug#333858: initrd/initramfs: we discussed enough, let's take some action now :)

[Sven Luther <sven.luther@wanadoo.fr>]

On Sat, Oct 15, 2005 at 11:41:07AM +0200, Jonas Smedegaard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sat, 15 Oct 2005 08:57:31 +0200
> Sven Luther <sven.luther@wanadoo.fr> wrote:
> 
> > > The patch claims support for 2.6.8, which is where development
> > > started, but later yaird versions only have had testing with
> > > newer kernels.  If we could get away with claiming a later version,
> > > that can only reduce number of bug reports.
> > 
> > Not a good idea, 2.6.8 is the sarge kernel, and it should be best to
> > keep at least 2.6.8 host systems in the compatibility list, for
> > sarge26 -> etch upgrades. Not sure about target system, anything
> > below 2.6.12 is rather academic there.
> 
> I believe that still running 2.6.8 even after upgrading to etch is
> quite realistic. Personally I would be sceptical to switching both
> ramdisk-generator and kernel version at the same time and choose to do
> a dpkg-reconfigure on the already installed kernel (after making a
> backup of the old working ramdisk) before upgrading to a newer one -
> especially if using funny stuff like encrypted rootfs or nfsroot.
> 
> In other words: If by "academic" you mean "unlikely to happen in
> reality" I disagree.

Well, etch will not ship with a 2.6.8 kernel, so the upgrade path to 2.6.8 is
not something we need to concern ourself with. the upgrade path from 2.6.8 is
another mather, especially if we do it in two steps like suggested above.

Friendly,

Sven Luther