From owner-freebsd-arch@FreeBSD.ORG  Tue Jun  3 23:14:34 2003
Return-Path: <owner-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 6AC0A37B401; Tue,  3 Jun 2003 23:14:34 -0700 (PDT)
Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E2F7D43F75; Tue,  3 Jun 2003 23:14:33 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org
	(12-232-168-4.client.attbi.com[12.232.168.4])
	by attbi.com (rwcrmhc52) with ESMTP
	id <2003060406143305200r1u3ge>; Wed, 4 Jun 2003 06:14:33 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA98153;
	Tue, 3 Jun 2003 23:14:32 -0700 (PDT)
Date: Tue, 3 Jun 2003 23:14:31 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Mike Barcroft <mike@FreeBSD.org>
In-Reply-To: <20030604011315.F70533@espresso.bsdmike.org>
Message-ID: <Pine.BSF.4.21.0306032300580.80038-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: arch@freebsd.org
cc: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: Making a dynamically-linked root
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2003 06:14:34 -0000



On Wed, 4 Jun 2003, Mike Barcroft wrote:

> 
> I think if we identify the dependency graph we can restrict the
> parallelization to only the leaf nodes.  Granted, we're probably
> missing some non-obvious dependencies in rc.d like the cron/sendmail
> one you mentioned.
> 

Given a lot of daemons allow their shell to continue almost immediatly,
how do you tell the difference between the daemon starting,
but destined to eventually fail, and starting and destined to succeed?

The fact that the shell continued with no error condition is not
any reflection as to whether the service (e.g an IP address in the case
of dhclient) is available yet or not.)

In the end every possible 'service' has to have its own 'test of
completion'.. e.g. "does fxp0 have an IP address yet?", or
"can we resolve a hostname yet?", or, "is /usr mounted yet".
We solved this on teh Interjet because we had a known set of services
and we literally hard-coded a lot of stuff.