From owner-cvs-all@FreeBSD.ORG Sat Apr 22 12:51:48 2006 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3EBC16A401; Sat, 22 Apr 2006 12:51:47 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (ns1.pittgoth.com [216.38.206.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58CF343D5C; Sat, 22 Apr 2006 12:51:45 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (ip70-177-190-239.dc.dc.cox.net [70.177.190.239]) (authenticated bits=0) by pittgoth.com (8.13.4/8.13.4) with ESMTP id k3MDuA1R014626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 22 Apr 2006 09:56:11 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Sat, 22 Apr 2006 08:51:43 -0400 From: Tom Rhodes To: Robert Watson Message-Id: <20060422085143.734e2f24.trhodes@FreeBSD.org> In-Reply-To: <20060422133933.A56433@fledge.watson.org> References: <200604210714.k3L7EQhD046878@repoman.freebsd.org> <20060421161321.J44089@fledge.watson.org> <20060421212322.2f5b3fa8.trhodes@FreeBSD.org> <1A949C80-E65D-4349-8028-8B0EB1A91D27@FreeBSD.org> <20060422001635.247a8b88.trhodes@FreeBSD.org> <20060422133933.A56433@fledge.watson.org> X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, jhb@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_vfsops.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2006 12:51:48 -0000 On Sat, 22 Apr 2006 13:45:35 +0100 (BST) Robert Watson wrote: > > On Sat, 22 Apr 2006, Tom Rhodes wrote: > > > Which is why I suggested that, similar to Linux, we make everything an > > option instead of either Warning before you build/install the new kernel or > > add the addition headache of turning it on later. Thus, I'm still of the > > opinion that one does not blindly add a newfs option during the install > > without understanding what's going on. > > The problem you're diagnosing is booting a kernel that doesn't support > features requested by the administrator. When this happens, there are really > only two things you can do: > > (1) Generate warnings and continue. > (2) Generate warnings and stop. > > We opt for (1) because it makes recovery easier. Deleting the warnings helps > neither case. Booting an SELinux system without an SELinux kernel will fail > in many spectacular ways, but I'm not sure if they generate a warning > equivilent to the one you deleted. > > BTW, turning on the multilabel flag in sysinstall is not an option offered by > the installer -- by setting it using sysinstall's "additional flags" field, > you're specifially doing something not part of the install path. The MAC Heh, exactly why I wanted to remove it. :) Someone would need a reason to do it this way, I was hoping in this case that someone would have a clue. It's reverted in any case. ;) -- Tom Rhodes