From owner-freebsd-arch@FreeBSD.ORG Thu Jan 18 15:48:35 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 170AC16A417; Thu, 18 Jan 2007 15:48:35 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id CC1A513C442; Thu, 18 Jan 2007 15:48:34 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id AD56A2089; Thu, 18 Jan 2007 16:13:44 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 3205B2087; Thu, 18 Jan 2007 16:13:44 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id 9C047B86E; Thu, 18 Jan 2007 16:15:00 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Craig Rodrigues References: <20070118134936.GA7391@crodrigues.org> Date: Thu, 18 Jan 2007 16:15:00 +0100 In-Reply-To: <20070118134936.GA7391@crodrigues.org> (Craig Rodrigues's message of "Thu, 18 Jan 2007 08:49:36 -0500") Message-ID: <86lkk02wp7.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount(8) can figure out fstype 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: Thu, 18 Jan 2007 15:48:35 -0000 Craig Rodrigues writes: > This is a different version of the patch I posted here: > http://lists.freebsd.org/pipermail/freebsd-arch/2006-July/005439.html Didn't somebody mention ordering issues back then? Your revised patch still doesn't even try to address those. If we ever get ext3 support, for instance, mounting an ext2 file system as ext3 might cause it to be silently upgraded to ext3. Not to mention the slew of error messages this will result in as you walk the list of filesystems trying to find the right one... A better way would be to have a userland utility attempt to identify the file system, and if necessary load the appropriate module, before mounting it. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no