From owner-freebsd-current@FreeBSD.ORG  Thu Mar  1 21:52:06 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 609C3106566C;
	Thu,  1 Mar 2012 21:52:06 +0000 (UTC)
	(envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
	by mx1.freebsd.org (Postfix) with ESMTP id 2CA768FC14;
	Thu,  1 Mar 2012 21:52:06 +0000 (UTC)
Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net
	[67.180.24.15]) (authenticated bits=0)
	by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id q21Lq0EJ077670
	(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
	Thu, 1 Mar 2012 13:52:01 -0800 (PST)
	(envelope-from julian@freebsd.org)
Message-ID: <4F4FEF85.2050308@freebsd.org>
Date: Thu, 01 Mar 2012 13:52:05 -0800
From: Julian Elischer <julian@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US;
	rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19
MIME-Version: 1.0
To: Devin Teske <devin.teske@fisglobal.com>
References: <4F26CC5A.2070501@FreeBSD.org>
	<4F4C0600.2000903@FreeBSD.org>	<3BA1B476-ED05-4E8E-8DFA-0B06EFB48867@samsco.org>	<201202280846.08966.jhb@freebsd.org>	<A8C72CB9-4C77-4697-8C28-63A2E10C557D@fisglobal.com>	<4F4F35B9.5090308@FreeBSD.org>
	<06bb01ccf7cb$b255a200$1700e600$@fisglobal.com>
	<4F4FE85D.4070205@freebsd.org>
	<074701ccf7f3$315cca20$94165e60$@fisglobal.com>
In-Reply-To: <074701ccf7f3$315cca20$94165e60$@fisglobal.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, 'Devin Teske' <dteske@vicor.com>,
	'Andriy Gapon' <avg@freebsd.org>
Subject: Re: revisiting tunables under Safe Mode menu option
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 21:52:06 -0000

On 3/1/12 1:35 PM, Devin Teske wrote:
> Right, making the assumption that FreeBSD's safe mode will do the same thing as
> Windows' safe mode is a poor assumption.
>
> As you point out, all those things that Windows safe mode does, FreeBSD does
> not.
>
> X11 drivers are not affected by safe mode.
>
> Network is not affected by safe mode.
>
> Services started at boot, are not affected...
>
> So I would welcome discussions involving development of something better (and am
> willing to help).

but, with help from the rc people. it could..
the kenv framework gives us a much more flexible way to implement the 
sysV runlevels that linux inherrited.

here's what I would envision:

a single safe mode switch
a way to control what that does (either 'safe mode' drops you to 
another menu which includes
"boot safe mode:" and "configure safe mode" (the second one drops you 
to yet another menu of check boxes).

the result of this is a preconfigured set of kenv entries being dumped 
into the kenv space.

The rc system can look at the kenv space for some key entries and act 
accordingly.
it can also SAVE to /boot/safe_mode.conf the set of kenv entries 
selected when safe mode is used,
and the forth code can load that and use it as a default on next 
'safe' mode usage.


BTW do we use the forth boot stuff on all architectures?
what of NFS boots?