From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 06:38:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB8D916A4D0 for ; Mon, 6 Dec 2004 06:38:00 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F46143D49 for ; Mon, 6 Dec 2004 06:37:58 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-68-123-122-146.dsl.snfc21.pacbell.net [68.123.122.146])iB66bp6M253484; Mon, 6 Dec 2004 01:37:52 -0500 Message-ID: <41B3FE3E.3070407@elischer.org> Date: Sun, 05 Dec 2004 22:37:50 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: Poul-Henning Kamp References: <57430.1102240929@critter.freebsd.dk> In-Reply-To: <57430.1102240929@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jeff Roberson cc: Garance A Drosihn cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 06 Dec 2004 06:38:00 -0000 Poul-Henning Kamp wrote: > In message <20041205044145.A18185@mail.chesapeake.net>, Jeff Roberson writes: > >>On Sun, 5 Dec 2004, Poul-Henning Kamp wrote: >> >> >>>In message , Garance A Drosihn writes: >>> >>>>At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: >>>> >>>>>http://phk.freebsd.dk/patch/rootfs.patch >>>>> >>>>>Please test and review. >>>> >>>>Hmm. Does this mean that we'll always get the correct partition >>>>for '/', even if /etc/fstab is wrong for '/'? By "correct", I >>>>mean "the partition that the kernel was loaded from". >>> >>>The loader reads /etc/fstab and picks the entry for '/' out of it >>>so I can only pressume that whoever did that disagree with your >>>notion of "correct". >> >>I believe he's referring to the case where you load a kernel from >>somewhere other than the default '/'. > > > I'm not sure, and I don't really care much. The order in which the > kernel tries various root filesystems is not affected apart from me > removing the "ask" mode which is badly implemented, prone to problems > and unecessary now that we can set it in the loader. Where it's not documented well enough to use in an emergency, while the "ask" mode had a good example right there in front of you.. saved my bacon several times. >