Bug 21423

Summary: Can't load kernel, after rebooting fresh-installed 5.0-CURRENT
Product: Base System Reporter: Makoto Matsushita <matusita>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.0-CURRENT   
Hardware: Any   
OS: Any   

Description Makoto Matsushita 2000-09-20 18:20:01 UTC
	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.

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.
How-To-Repeat: 
	- Prepare Fresh PC
	- Install 5.0-CURRENT via your favorite media (CD, ftp, etc)
	- reboot
Comment 1 Makoto Matsushita 2000-09-27 05:17:57 UTC
Here is a status report of this PR. To announce more wider audiences,
this mail is also sent to current@freebsd.org.

* This PR keeps all committers away. No lucks.

* If you want to install 5.0-CURRENT to a *fresh* PC, you'll be warned
  that your PC cannot find the kernel location.

-- -
Makoto `MAR' MATSUSHITA
Comment 2 jkh freebsd_committer freebsd_triage 2000-09-29 08:46:43 UTC
State Changed
From-To: open->closed

I thought there would be more contraversy to play out over 
the move to /boot/kernel, but evidently not so I'll fix 
it now.  :)  Thanks for the report.