[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#255244: base-installer: granular kernel selection



On Sat, Jun 19, 2004 at 08:54:39PM +0200, martin f krafft wrote:
> Standard mode:
> 
>   - use the kernel-image-2.x-y package corresponding to architecture
>     and kernel used for the installation. that package depends on
>     the latest kernel in that series, which is what most users will
>     want.
>   - if the install was with a 2.4 kernel, consider asking the user
>     whether to install 2.4 or 2.6. if it was done with a 2.6 kernel,
>     then use 2.6 since it may be required for the hardware.

It's possible for there to be regressions from 2.4 to 2.6. I think the
current behaviour is fine, i.e. default to and prefer what the installer
is using, but allow the other one if necessary.

If somebody for whatever reason produces a CD containing only the 2.4
kernel-image .deb but using 2.6 d-i, then it's better to install the 2.4
kernel-image than to install no kernel at all.

>   - ask whether to use a 'specific kernel', or the 'latest in the
>     series'.

That's very difficult to do across architectures (also, note that not
all architectures have the kernel-image-2.x-* tracker packages), and I'm
not sure it's all that useful.

>   - depending on the answer, show a list of 2.x.y-<arch> packages or
>     2.x-<arch> packages (which depends on the latest 2.x.y-<arch>
>     package) respectively.

base-installer already shows you a list of kernels at low priority. Part
of the point of my experimental branch is to allow the list to be
trimmed down to only those kernels which will work.

I think I've now lost track of what you're asking for in terms of a
delta from the current code ...

Cheers,

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]



Reply to: