Bug 18923 - boot0cfg(8) cannot select default boot slice
Summary: boot0cfg(8) cannot select default boot slice
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: i386 (show other bugs)
Version: 3.4-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: dwmalone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-05-31 23:20 UTC by iedowse
Modified: 2000-08-17 19:43 UTC (History)
0 users

See Also:


Attachments
file.diff (3.42 KB, patch)
2000-05-31 23:20 UTC, iedowse
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description iedowse 2000-05-31 23:20:02 UTC
	boot0cfg(8) currently has no way to select the default boot
	slice. Having such a mechanism is useful when boot0 is used
	with the `noupdate' option. Since turning on `noupdate'
	for the first time requires booting FreeBSD (which makes
	FreeBSD the default), there is no direct way to make some
	non-FreeBSD partition the permanent default.

	[Indirect ways to achieve this which do work include booting
	FreeBSD from a floppy or CDROM (so as not to disturb the current
	default slice) and then running boot0cfg, or manually editing
	the byte at offset 0x1b9 in the MBR.]

	The patch included below adds a new `-s' option to boot0cfg
	that allows the default boot slice to be configured.

Fix: Apply the following patch in src/usr.sbin/boot0cfg.
How-To-Repeat: 
	- Take a disk with two slices:

		F1 Dos
		F2 FreeBSD

	- Attempt to make "F1 Dos" the permanent default, so it will
	always be the default regardless of the last selection made.

	- Discover that in order to run "boot0cfg -o noupdate", one must
	first boot FreeBSD. Running "boot0cfg -o noupdate" then makes
	"F2 FreeBSD" the permanent default.
Comment 1 dwmalone freebsd_committer freebsd_triage 2000-07-11 12:39:12 UTC
Responsible Changed
From-To: freebsd-bugs->dwmalone

Local PR.
Comment 2 dwmalone freebsd_committer freebsd_triage 2000-08-17 19:42:45 UTC
State Changed
From-To: open->closed

Committed.