> Everyone,
> Note: I'm not a developer, so the following comments may be out of line.
>
> I think we're drifting from the purpose LEAF was started for. I thought we
> agreed that we weren't going to create an embedded distribution. This
means
> we wouldn't create our own kernel patches, and we would remain embedded
> distribution neutral.
>
> I thought we started this project to create network centric target
> environments for specific purposes. I thought we were going to wait for an
> embedded Linux distribution to include 2.4 support before creating target
> environments. I also thought we were trying to maintain the ability to
> install the target environment on a floppy. See the taxonomy below for my
> interpretation of the differences between LRP/Butterfly and the LEAF
project.
A good point...I am sort of wandering afield, but the bug has bitten me to
start playing with a 2.4 kernel in LRP. To do this, the initrd_archive
patch Dave C. wrote needs to be hacked into the 2.4 ramdisk driver. I could
wait for Dave C. to do this himself (and share with the world), but it's a
good introduction to the kernel code, and even though I should probably be
updating my website, releasing a new disk image, or updating various
packages, sometimes you just have to do things that are fun. Current
status: The archive is being uncompressesed, and the minix filesystem is
being created, but the kernel is still crashing (I think in the untar
routine, but I'm not sure). I think everything will be working soon... My
current plans are to play with the 2.4 kernel in my Eiger distributions and
see how much stuff breaks ;-)
BTW: I will be off work from Dec 15th through the new year (we get
christmas to new-years off, and I'm taking an extra week, too), so I'll
probalby do lots of 'LRP grunt work' then...
> Note: I haven't finished reading the on-line documentation for CVS, so
this
> structure is probably wrong.
>
> I suggest the following structure for CVS:
>
> /eigerstein +
> +- ?
> /oxygen +
> +- ?
>
> /doc +
> +- devel_guide
> +- etc.
>
> /web +
> +- images
> +- devel_pages +
> + mhnoyes
> + etc.
>
> Charles and David should determine what is included in their sub
> directories. Developers can help with either distribution as they see fit,
> or create their own based on another embedded Linux distribution. The
> distributions should have the freedom to merge or diverge. The best ones
> will draw developers that want to contribute, while the weak will perish.
This sounds good to me. I may only partly fill out the eigerstein
directory, as I sort of intend to work on a new distribution, drawing from
the combined efforts of Dave's 2.9.8, Matthew's Eiger, my extended scripts,
my LRP-CD work, and some other ideas I've got... Lack of time and the
general fact that I didn't really do the bulk of the 'creation' work for the
EigerStein distribution (I mainly just added packages & updated config
files) will likely limit how much gets loaded into CVS.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/leaf-devel
