Crash while upgrading kernel & stable releases

Vincent Untz vincent at vuntz.net
Mon Jun 20 10:11:12 CDT 2005


On Mon, June 20, 2005 16:59, Markus Kolb said:
> Vincent Untz wrote on Mon, Jun 20, 2005 at 16:09:30 +0200:
>> That's the problem, indeed. The problem is: why is the new package named
>> linux-image-2.6.10-5-686, while it could be linux-image-2.6.10-6-686 or
>> linux-image-2.6.10-5-686-fix1 or...?
>
> That would enable the possibility to install the upgraded kernel
> together with the older one.
> But package management would not detect that there is an updated kernel
> package available because package name is different to the older one.
> For package manager it would be a total different package with no
> relation to the old installed package.
>
> A solution would be so far to use a metapackage which depends on the
> up-to-date kernel package and kernel package depends back to the
> metapackage. So installing a kernel package would install the
> metapackage which is responsible for updates.
> If there is an updated kernel package with new package name the
> metapackage must be updated to depend on this new kernel package.
> The metapackage should also suggest any older kernel package for
> installation or the old kernel package will be marked for deinstallation
> on upgrades.
>
> When running the updated kernel the older kernel packages can be
> deinstalled by user if he/she wants.
>
> I think that would do it.

We already have this: linux-image-686 :-)
Else, you would not be able to upgrade from Warty to Hoary, etc.

Vincent

-- 
Les gens heureux ne sont pas pressés.



More information about the ubuntu-devel mailing list