From owner-freebsd-small@FreeBSD.ORG Thu Sep 15 12:49:35 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 BB94216A41F for ; Thu, 15 Sep 2005 12:49:35 +0000 (GMT) (envelope-from snoel@gestosoft.com) Received: from mail.networksolutionsemail.com (mail.networksolutionsemail.com [205.178.146.50]) by mx1.FreeBSD.org (Postfix) with SMTP id 2FD7343D45 for ; Thu, 15 Sep 2005 12:49:34 +0000 (GMT) (envelope-from snoel@gestosoft.com) Received: (qmail 26227 invoked by uid 78); 15 Sep 2005 12:49:34 -0000 Received: from unknown (HELO webmail13) (205.178.146.50) by mail.networksolutionsemail.com with SMTP; 15 Sep 2005 12:49:34 -0000 Received: from 204.101.154.2 (unverified [204.101.154.2]) by webmail13 (VisualOffice 4.01) with WEBMAIL id 13746; Thu, 15 Sep 2005 12:49:34 +0000 From: "Sandro Noel." To: gnn@neville-neil.com, "Sandro Noel" Importance: Normal Sensitivity: Normal Message-ID: X-Mailer: Mintersoft VisualOffice, Build 4.01.1003 X-Originating-IP: [204.101.154.2] Date: Thu, 15 Sep 2005 12:49:34 +0000 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--=_vm_0011_W8756211063_13746_1126788574" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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, 15 Sep 2005 12:49:35 -0000 ----=_vm_0011_W8756211063_13746_1126788574 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit >That is the usual approach but again, not easy. You need to track >modules and versions so that you can know if things will fit together >at the end. I would hold this part to the very end, after the >architecture of the modules is well understood. >Good, but let's keep that for later. The approaches taken in nano and >pico bsd of using the build system itself are a good start. Yes that is the idee, from source, just like the port tree. >Doxygen can help us here, but it will take a bit of horsepower for the >whole kernel. Take a look at the doxygen docs and you'll see that it >will generate this. We just have to be careful not to do it from root >and then to annotate the code to fix errors in the automatic >generation phase. i'm looking into it... but i must admit it's a mistery to me right now. >So, that's fine. I think the documentation/cutting up step has to >come first, which is often frustrating to people who like to mostly >code, but I just don't see a way around making the map. I dont have a problem with that, I just need a good starting point. and something to look for. >How much time do you think you have to put into this? A couple of hours a day, mostly after 7:00pm EST You seem to have more knowlage than I do here, would you like to take lead in this project? Something i want to calrify, it is not just about the kernel and it's drivers"modules" tought it is the starting point of the system, i also want to map the system features like networking ppp, bluetooth, mostly everything that ships with the system sources that is not already into a port tree or a package. ----=_vm_0011_W8756211063_13746_1126788574--