Date: Thu, 21 Sep 2000 02:17:17 +0900 From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/21423: Can't load kernel, after rebooting fresh-installed 5.0-CURRENT Message-ID: <20000921021717P.matusita@jp.FreeBSD.org>
next in thread | raw e-mail | index | archive | help
>Number: 21423 >Category: bin >Synopsis: Can't load kernel, after rebooting fresh-installed 5.0-CURRENT >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Sep 20 10:20:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Makoto MATSUSHITA >Release: FreeBSD 5.0-CURRENT i386 >Organization: Japan FreeBSD Users' Group >Environment: 5.0-CURRENT, after kernel location was changed from / to /boot/kernel >Description: Default kernel location was changed from /kernel to /boot/kernel/kernel, but sysinstall doesn't know about this. If you installed 5.0-CURRENT to a fresh PC and reboot, you should see "can't load kernel" message. >How-To-Repeat: - Prepare Fresh PC - Install 5.0-CURRENT via your favorite media (CD, ftp, etc) - reboot >Fix: installFixupBin() in src/release/sysinstall/install.c should consider new default kernel path. Moreover, /kernel.GENERIC shouldn't be there. Maybe /boot/kernel is prefered. We can modify 'release.3' target of src/release/Makefile to do that. Sorry, no patch is made... but it is easy to hack. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000921021717P.matusita>