From owner-freebsd-small@FreeBSD.ORG Thu Sep 8 22:28:38 2005 Return-Path: X-Original-To: freebsd-small@freebsd.org Delivered-To: freebsd-small@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EAD616A41F for ; Thu, 8 Sep 2005 22:28:38 +0000 (GMT) (envelope-from snoel@gestosoft.com) Received: from toq7-srv.bellnexxia.net (toq7-srv.bellnexxia.net [209.226.175.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D74943D45 for ; Thu, 8 Sep 2005 22:28:37 +0000 (GMT) (envelope-from snoel@gestosoft.com) Received: from [10.0.5.52] ([69.159.107.216]) by tomts40-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20050908220101.JSYQ1799.tomts40-srv.bellnexxia.net@[10.0.5.52]>; Thu, 8 Sep 2005 18:01:01 -0400 In-Reply-To: References: <20050908165951.GE31354@odin.ac.hmc.edu> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sandro Noel Date: Thu, 8 Sep 2005 18:00:45 -0400 To: "George V. Neville-Neil" X-Mailer: Apple Mail (2.734) Cc: freebsd-small@freebsd.org Subject: Re: System Tree essentials UNDERSTANDING the system X-BeenThere: freebsd-small@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2005 22:28:38 -0000 On Sep 08, 2005, at 1:42 PM, George V. Neville-Neil wrote: > Doxygen George I second that. I've just had a look at it quickly, and i was going to propose building a database to organize the information but this seems right. I was thinking of - let me know if you share this vue - organizing the base system into features, something like Starting point is from source CVS whatever branch. to boot the really bare minimum system you need [ information here ] ( at this point the system does nothing useful ) to control multiple user you need [ passwd useradd .... whatever ] to boot to a shell you need [ information here ] to add networking to the system you need [ information here ] to add this and that feature to your system ........ and so on, for the main features, and those main features would be sub devided into Kernel options to include ( if apply ) Kernel modules to load at init ( if apply and if the kernel does not do it on itself) executables to include ( and why, what is the use ) Libraries to include ( and why ) configuration files to adjust (with links to man pages if apply) dependencies ( on other features, or on anything else ) links that need to be changed or updated devices nodes that need to be created if devfs does not do it. now, i guess this brings a question, is it possible to devide the system into smaller blocks like that, while still keeping it functional. as an example. is it possible to boot the system to a shell without any user files on the system. or any groups for that matter. if breaking the system into smaller parts is possible without rendering the system unusable then, i think this just might work... Sandro Noel snoel@gestosoft.com