From owner-freebsd-current@FreeBSD.ORG Thu Mar 1 01:35:19 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A2FE106564A; Thu, 1 Mar 2012 01:35:19 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 2FB168FC0A; Thu, 1 Mar 2012 01:35:18 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa05 [127.0.0.1]) by ltcfislmsgpa05.fnfis.com (8.14.4/8.14.4) with SMTP id q211PJwW031330; Wed, 29 Feb 2012 19:34:58 -0600 Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa05.fnfis.com with ESMTP id 139yahg18w-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 29 Feb 2012 19:34:58 -0600 Received: from [10.0.0.101] (10.14.152.61) by smtp.fisglobal.com (10.132.206.16) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 29 Feb 2012 19:34:56 -0600 MIME-Version: 1.0 (Apple Message framework v1257) From: Devin Teske In-Reply-To: <201202280846.08966.jhb@freebsd.org> Date: Wed, 29 Feb 2012 17:34:55 -0800 Content-Transfer-Encoding: quoted-printable Message-ID: References: <4F26CC5A.2070501@FreeBSD.org> <4F4C0600.2000903@FreeBSD.org> <3BA1B476-ED05-4E8E-8DFA-0B06EFB48867@samsco.org> <201202280846.08966.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1257) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7498, 1.0.260, 0.0.0000 definitions=2012-02-29_06:2012-02-29, 2012-02-29, 1970-01-01 signatures=0 Content-Type: text/plain; charset="iso-8859-1" Cc: freebsd-current@freebsd.org, Devin Teske , Gapon , Andriy 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2012 01:35:19 -0000 On Feb 28, 2012, at 5:46 AM, John Baldwin wrote: > On Tuesday, February 28, 2012 1:23:11 am Scott Long wrote: >> I still think that it's useful to be able to disable ACPI. Just because= =20 > ACPI works well on modern hardware doesn't mean that everything crummy fr= om=20 > 2000-2007 suddenly disappeared off the face of the earth. But I agree th= at=20 > turning it off on modern systems probably does more harm than good. Henc= e my=20 > suggestion for a finer control over this in the menu. Maybe Devin Teske = can=20 > lend some help with this task? .oO(uh oh, what'd I do now?) > For extra credit, it should be possible to=20 > write a simple static analysis tool that collects all of the tunables tha= t are=20 > compiled into the kernel and generates a data file that the boot menu can= =20 > process and turn into interactive knobs for the user. >=20 > Hmm, with the newer boot menu, can't one now toggle safe mode and ACPI=20 > independently? Semi-independently; ordered rather. Toggling Safe Mode On will toggle ACPI Off. This is the only real example o= f one menu item reaching into another menu item, and it only happens when t= oggling Safe Mode on (not off). Despite the above description, it is in-fact intuitive and the effects are = as-expected. Booting Safe Mode with ACPI enabled is no harder than toggling Safe Mode on= [first] before [then] re-enabling ACPI (followed by ENTER). > (Assuming we haven't removed the ability to disable ACPI from=20 > the menu, if we have we should perhaps put that back). Having them be=20 > orthogonal knobs would seem to the be the best approach. >=20 +1 on keeping the menu items loosely entwined (ACPI stands alone, but Safe = Mode knows about ACPI but only acts on it when being enabled). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.