From owner-freebsd-arch@FreeBSD.ORG Mon Jul 10 20:39:57 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 167B416A4DA; Mon, 10 Jul 2006 20:39:57 +0000 (UTC) (envelope-from SRS0+82d3cd74a67493595751+1051+infradead.org+hch@pentafluge.srs.infradead.org) Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3C7A43D49; Mon, 10 Jul 2006 20:39:56 +0000 (GMT) (envelope-from SRS0+82d3cd74a67493595751+1051+infradead.org+hch@pentafluge.srs.infradead.org) Received: from hch by pentafluge.infradead.org with local (Exim 4.62 #1 (Red Hat Linux)) id 1G02Xl-0008AL-Q5; Mon, 10 Jul 2006 21:39:49 +0100 Date: Mon, 10 Jul 2006 21:39:49 +0100 From: Christoph Hellwig To: Scott Long Message-ID: <20060710203949.GA31267@infradead.org> References: <20060708152801.GA3671@crodrigues.org> <44AFD7DF.8090002@errno.com> <20060708174606.GA29602@infradead.org> <44B2A51A.4040103@samsco.org> <20060710202219.GA29786@infradead.org> <44B2B8DC.8070201@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B2B8DC.8070201@samsco.org> User-Agent: Mutt/1.4.2.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Cc: freebsd-arch@freebsd.org, freebsd-current@freebsd.org, Craig Rodrigues Subject: Re: [RFC] mount can figure out fstype automatically X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 20:39:57 -0000 On Mon, Jul 10, 2006 at 02:30:20PM -0600, Scott Long wrote: > >lead to all kinds of funnies. Linux does this (iterating all filesystem > >types in kernel) for the special case of the root filesystem where mount(8) > >is not available, and it showeds various interesting bugs at least in the > >fat driver. > > > > How does it resolve situations like with UDF vs iso9660, where both > structures can co-exist? The kernel doesn't do anything fancy. It just walks the list of filesystem and the first fs that takes it gets it. To answer the specific example iso9660 is registered before udf so if you wanted to use a dual-fs cdrom as root you would get iso9600 unless you specified the rootfstype=udf boot option.