Subject: install/16409: i386 default sysinst doesn't install a kernel
To: None <email@example.com>
From: None <kre@munnari.OZ.AU>
Date: 04/19/2002 18:28:21
>Synopsis: i386 default sysinst doesn't install a kernel
>Arrival-Date: Fri Apr 19 04:28:00 PDT 2002
>Originator: Robert Elz
>Release: NetBSD-current 2002-04-18
Prince of Songkla University
System: NetBSD jade.coe.psu.ac.th 1.5ZC NetBSD 1.5ZC (JADE) #1: Sun Mar 31 12:48:10 ICT 2002 firstname.lastname@example.org.OZ.AU:/usr/obj/sys/JADE i386
(This is the system that send-pr was run on...)
For -current sysinst (with the choice of kernels) all the
kernels default to off. That's no problem for a custom
install (which most of us probably do), but for anyone who
does one of the "standard" installs, they end up with a system,
that has no /netbsd (nor any of the varians /boot knows) and
which consequently cannot boot.
Do a NetBSD-current full install, and select either "standard" or
"standard with X" (not "custom"). Reach the end of the install,
and reboot [aside: the "panic: init died" does not seem to be fixed
yet - I'm pretty sure I made this after that was supposed to have
been fixed]. The reboot will loop forever attempting to find
/netbsd /onetbsd /netbsd.gz (etc), finding none of them.
It also seemed as if it might be possible to select (and install)
more than one kernel set (when doing a custom install). Since
I assume they each produce /netbsd that would not be a good idea.
sysinst needs to know there are alternatives, select only one
(a niceish way to do that would be to allow only one set for each
"base name" where the base name here is the part that precedes the
last '-' in the anme).
Change sysinst to enable one of the kernel sets by default
(which one will depend upon which version of the boot floppy it
is being installed on - on the "normal" ones, kern-GENERIC should
be enabled, on the laptop floppies, a laptop kernel, on the tiny boot
floppy, a "tiny generic" shoudl bethe default, etc...).