From owner-freebsd-hackers  Thu Sep 16  7:53:43 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id E493A156FC; Thu, 16 Sep 1999 07:53:40 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA77463;
	Thu, 16 Sep 1999 08:53:38 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA21647; Thu, 16 Sep 1999 08:53:08 -0600 (MDT)
Message-Id: <199909161453.IAA21647@harmony.village.org>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Subject: Re: panic() the system from the console (was: Re: kern/13721: There is no way to force system panic from console) 
Cc: hackers@FreeBSD.ORG, sos@FreeBSD.ORG, bde@FreeBSD.ORG
In-reply-to: Your message of "Thu, 16 Sep 1999 18:48:13 +0900."
		<199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp> 
References: <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp>  
Date: Thu, 16 Sep 1999 08:53:08 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp> Kazutaka YOKOTA writes:
: 	case _PANIC_KEY_
: #if !defined(SC_DISABLE_REBOOT) && !defined(SC_DISABLE_PANIC)
: 		if (securelevel <= 0)
: 			panic();
: #endif
: 		break;
: 
: Any opinions?

I can see this being useful only for systems that have a problem
coming up.  Otherwise, adding options SC_DISABLE_{PANIC,REBOOT} would
accomplish this as well.  So I'm mildly opposed to this since it hangs
yet another thing on securelevel...

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message