Subject: bin/23345: installboot should complain about securelevel > 0
To: None <gnats-bugs@gnats.netbsd.org>
From: None <perry@piermont.com>
List: netbsd-bugs
Date: 11/02/2003 10:40:59
>Number:         23345
>Category:       bin
>Synopsis:       installboot should complain about securelevel > 0
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 02 15:42:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Perry E. Metzger
>Release:        NetBSD 1.6ZC
>Organization:
Perry E. Metzger		perry@piermont.com
--
"Ask not what your country can force other people to do for you..."
>Environment:
	
	
System: NetBSD alchemist 1.6ZC NetBSD 1.6ZC (ALCHEMIST) #0: Mon Sep 22 14:13:46 EDT 2003 perry@alchemist:/usr/src/sys/arch/i386/compile/ALCHEMIST i386
Architecture: i386
Machine: i386
>Description:
	The error message put out by installboot when attempting to
	install boot blocks on a mounted file system when securelevel > 0
	is cryptic. It should be easy to tell the user that the
	problem is that the securelevel is too high and complain about
	that directly to alleviate confusion.
>How-To-Repeat:
	Attempt to install bootblocks on a mounted file system when
	securelevel is > 0. Get cryptic error message.
>Fix:
	If the device exists but can't be written, check if
	securelevel is > 0 and the device is mounted, then complain
	about that.
>Release-Note:
>Audit-Trail:
>Unformatted: