From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 13:23:28 2003 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 0FC7437B401 for ; Thu, 10 Jul 2003 13:23:28 -0700 (PDT) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 486E443F75 for ; Thu, 10 Jul 2003 13:23:25 -0700 (PDT) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h6AKMvw19567; Thu, 10 Jul 2003 17:23:03 -0300 Message-ID: <3F0DCB21.1060704@tcoip.com.br> Date: Thu, 10 Jul 2003 17:22:57 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030702 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Andrew Kenneth Milton References: <3EF1ABDF.8080605@earthmagic.org> <3135.1056026240@critter.freebsd.dk> <20030619124850.GI476@zeus.theinternet.com.au> In-Reply-To: <20030619124850.GI476@zeus.theinternet.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: FreeBSD-rc@yahoogroups.com Subject: Re: support for mounting md(4) based filesystem at boot [PATCHES] 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: Thu, 10 Jul 2003 20:23:28 -0000 Andrew Kenneth Milton wrote: > +-------[ Poul-Henning Kamp ]---------------------- > | > | I think we need somebody to reconsider how we configure our filesystems > | in the future, in order to avoid a confusion of config files whose > | interrelationship users will have no chance of figuring out. > | > | We have CCD, GBDE, MD and in the future likely other technologies for > | configuring the underlying devices, we have FSCK, UFS and NFS and > | other filesystems to mount. > | > | Somebody must be able to come up with some creative stuff here... ? > > We want .... > > A REGISTRY! > > Ni! Ni! Ni! Ni! Ni! Ni! Bah. Add a prerequisites field to fstab with all the filesystems that must be mounted before that one can be mounted. Then just teach mountlocal and mountremote to iterate mounting until no new filesystems can be mounted. Maybe we should add a "remote" flag to fstab, and make the rc.d script read fstab itself instead of relying on mount to know which filesystems are local and which are remote. The rc.d scripts can then extract that info and benefit from it in two ways: 1) It will know which filesystems can be mounted before network, and which require network. 2) The filesystems themselves could be used in BEFORE or REQUIRE. Mmmmmm. Either rcorder gets taught about this improved fstab, or we would have to add a program that reads fstab and then generates rc.d scripts as appropriate. Not sure I like the latter, but it has the advantage of keeping rcorder simple. Just food for thought. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Love means having to say you're sorry every five minutes.