From owner-freebsd-current Thu Dec 12 9:13:48 2002 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 B716937B404 for ; Thu, 12 Dec 2002 09:13:46 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B3E643EA9 for ; Thu, 12 Dec 2002 09:13:44 -0800 (PST) (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 gBCHDNV04924; Thu, 12 Dec 2002 15:13:28 -0200 Message-ID: <3DF8C3B3.2060601@tcoip.com.br> Date: Thu, 12 Dec 2002 15:13:23 -0200 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021212 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Brad Knowles Cc: kientzle@acm.org, current@FreeBSD.ORG Subject: Re: RC NG, ntp and routed References: <3DF7E948.9060508@acm.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Brad Knowles wrote: > At 5:41 PM -0800 2002/12/11, Tim Kientzle wrote: > > > The point of the barrier scripts is to provide > > simple dependencies to other scripts. In particular, > > NETWORKING should represent a fully-functional > > network, including any routing or multicast routing that is > > normally used on this network. It does not, in itself, depend > > on any filesystems. (It runs no programs itself, so why would it?) > > > Sure it does. In order to do anything, you have to run programs -- > right? And where do those programs come from -- a filesystem, right? > And what if that filesystem is not local, but mounted via NFS? So, you > need a way to bootstrap the early parts of networking before mounting > the later filesystems. This I disagree with. Networking should bring the network up. If something is necessary to bring the network up, it should be available locally. Remote filesystems should come _after_ the network is up. If a program needed to bring networking up is on a remote fs, then there is a problem with the system project. If it so happens to work without a fully functional network, good for it, but it's designer must shoulder the burden of supporting it. The standard way of doing things should be get the network up, and _then_ mounting the remote fs. Daemons which _depend_ on network are not part of networking, of course. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO 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 A day without orange juice is like a day without orange juice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message