From owner-freebsd-current@FreeBSD.ORG Tue Jul 5 00:22:44 2005 Return-Path: X-Original-To: current@freebsd.org 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 4012116A41C; Tue, 5 Jul 2005 00:22:44 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2469F43D45; Tue, 5 Jul 2005 00:22:44 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id j650LYFZ079316; Mon, 4 Jul 2005 17:21:35 -0700 (PDT) Date: Tue, 05 Jul 2005 09:21:34 +0900 Message-ID: From: gnn@freebsd.org To: "Poul-Henning Kamp" In-Reply-To: <29260.1120471829@phk.freebsd.dk> References: <29260.1120471829@phk.freebsd.dk> User-Agent: Wanderlust/2.12.2 (99 Luftballons) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Robert Watson , current@freebsd.org, Garance A Drosehn Subject: Re: Summary: experiences with NanoBSD, successes and nits on a Soekris 4801 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 05 Jul 2005 00:22:44 -0000 At Mon, 04 Jul 2005 12:10:29 +0200, Poul-Henning Kamp wrote: > > In message , gnn@freebsd.org writes: > >At Mon, 04 Jul 2005 10:25:34 +0200, > >Poul-Henning Kamp wrote: > >> I played with developing that graph by removing lines from LINT > >> and see what compiled and what didn't. Based on the progress I > >> made I would estimate the full graph will take about 1 CPU-year to > >> calculate by trial&error. > > > >Hmm. Well, either I need a very fast CPU, or a more clever approach. > >I guess we'll see... > > This was a dual Opteron, 2GHz, 4GB. > > It might be possible to do a less brute force and more analytical > approach: > > Start out with sys/conf/files*, then add sys/conf/options. > > Then for each and every .c file, grep out the #includes and > build a tree of complete _potential_ dependencies. > > Also grep out all #ifmumble constructs and record those. > > You now have a huge data structure from which it should be possible > to determine potential dependencies. > > Ie: Which source files could possibly be affected by this option > or conversely, which options could possibly affect this source file. > > By pruning the trival cases from the data structure, the brute force > work would be a lot less. Another thought I had was just going through the startup sequence Later, George