Bug#255244: base-installer: granular kernel selection
martin f krafft
Version: 20060616
Severity: wishlist
The kernel selection should be improved. In the following, I am
assuming that the optimisation level can be autodetected. Using
uname(1) or /proc/cpuinfo, this should not be a problem. I suggest:
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.
Expert mode:
- ask the user whether to install 2.4 or 2.6, if the
install was with a 2.4 kernel. if it was done with a 2.6 kernel,
then use 2.6 since it may be required for the hardware.
- ask whether to use a 'specific kernel', or the 'latest in the
series'.
- 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.
Thanks,
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (600, 'testing'), (98, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.6-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8
--
Please do not CC me when replying to lists; I read them!
.''`. martin f. krafft <mad...@debian.org>
: :' : proud Debian developer, admin, and user
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
Colin Watson
> 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 [cjwa...@flatline.org.uk]
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org