Well, it looks like my absense from home (and minimal time to work on LRP)
will continue for a while. Current plans call for me to be gone for about a
week starting April 2, gone for a bit more than a week towards the end of
April & first of May, then gone for 2-3 weeks starting mid-May. I'll be
traveling down to TX to do more move-related work and use the machine-shop
the compay owner has setup for building a new robot.
With the time I have available, I'd like to focus on getting a few key
things going. I plan to wrap up my HOWTO on turning LRP 2.9.8 into a
thin-server platform with root on the HDD. This should help open up new
applications for LRP, and will begin my transition from Materhorn/Eiger to
the 'official' LRP tree.
I'd also like to see work begin on a 2.9.8 based replacement for EigerStein.
This work should be done using the SourceForge resources as much as possible
to promote contributions by multiple developers. I'm not sure the best way
to structure development, but I think a CVS tree for each disk image that
contains modified configuration files is a good way to start. An "addon"
LRP package (or straight tar.gz file) could be made of the modified files,
and applied to a raw 2.9.8 image with the appropriate LRP packages added on.
If anyone has ideas about how best to manage making various disk images with
SourceForge, or wants to volunteer to set up a structure, please speak up.
Also, since I plan on using SeaWall for the new images, is there anyone
on-list who consideres themselves a resident expert on SeaWall? I'll
probably become one, but am currently starting at 'ground zero'.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
