Date: Wed, 14 Sep 2005 19:08:15 -0700 From: gnn@neville-neil.com To: Sandro Noel <snoel@gestosoft.com> Cc: freebsd-small@freebsd.org Subject: Re: System Tree essentials UNDERSTANDING the system Message-ID: <m27jdjozg0.wl%gnn@neville-neil.com> In-Reply-To: <41EC4892-A45A-4C77-A870-6E814863B2C5@gestosoft.com> References: <W903802119519351126194088@webmail2> <20050908165951.GE31354@odin.ac.hmc.edu> <m2vf1bwj69.wl%gnn@neville-neil.com> <E42CAEEC-0382-44D3-8A9D-38E1B3AE7B4E@gestosoft.com> <m23bofvvm1.wl%gnn@neville-neil.com> <41EC4892-A45A-4C77-A870-6E814863B2C5@gestosoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 13 Sep 2005 17:09:20 -0400, Sandro Noel wrote: > > It's not original to me, I have seen whole RTOSs shipped with the > > kernel APIs and docs in the code and then extracted by a similar > > method. > > > i like that, approach, i was thinking that once this maping of the > system into "features" it should be possible to have some kind of > system builder. > 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. > i picked around the net for such tool, and there happens to to exist > 2 somewhat worthy applications in the "linux" world, the infamous > ALFS, that i never got to work past some point of compilation. and > there is another one named I missed a word here, what's the second one? > something in that area would be great, and features could be added > to the build scripts.. and ports could be included as features .. > and so on ... i'm getting way ahead here . but wouldn't it be good > for BSD to have such tool ? 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. > > We ought to generate a map somehow... Hmmm. Have to think about > > that. > > yes . that is what i was thinking about too , maybe some king of > XML, inspired by the theory behind the ports system i'm wondering if > UML models would somehow apply here, it could generate the XML. i'm > just throwing ideas. > 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. > well that makes 2 of us. let's get organized. 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. How much time do you think you have to put into this? Later, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m27jdjozg0.wl%gnn>