Hi Christoph,

> after studying the LEAF-Bering Install and User Guides and analyzing 
> the /linuxrc script and the leaf.cfg structure I found out the most important 
> things. But the Bering-uClibc-2.3-beta5 is not covered in  the mentioned 
> guides. These guides only speak of the 1680kB floppy, which I have never seen 
> up to now. But the CDROM version is too young for these documents.
what part of http://leaf.sourceforge.net/doc/guide/bucu-ide.html misses
essential points about the CDROM version? I'm asking because if there is
something that's lacking proper documentation, this needs to be worked
on (but so far, all of the developers feel things are properly
documented). If you can point out some parts that need better
documentation, we'd be glad for the input (as always, patches/new
chapters for the docs are especially welcome, but simply giving ideas
about things that need more work are good as well).

I'm not sure what you needed to look for in linuxrc (unless you're
trying to do something rather advanced - in which care the _user_
documentation for leaf will most likely not be of much help). I'm rather
sure that no user ever needs to look through linuxrc to figure out how
to set up a leaf box (if not, we've done a pretty bad job ad documenting
things). But maybe that's just due to the fact that I don't understand
what exactly you're trying to do, that needs such intimate knowledge of
the inner workings of the boot process of a leaf box.

Martin


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to