Hello Charles, you wrote
> Well, I'm working on re-organazing my website, getting it into CVS, and
> migrating to new web development tools, but I'd like to get discussion
> started on another task high on my priority list: making new disk images.
>
> I propose the following:
>
> 1) EigerStein2Beta is upgraded with a current weblet.lrp and dhclient.lrp,
> released as EigerStein2 (non-beta), and left at that.
>
hmm, well it is your image.
> 2) A new disk image is created with some (or all) of the following
> characteristics:
> A) Based on 2.9.8, bringing it 'back into the fold' of "Official" LRP
> B) Repace Dave's pentium 2.2 kernel with one of the available 2.2.18
> kernels compiled for 486's
> C) Use SeaWall for firewalling rules (The Materhorn/Eiger scripts are
> fine, but limited when you need to do more than they planned for, plus I
> seem to be the only one maintaining them...I'd rather help the SeaWall guys
> & get a larger user base)
> D) Add nifty add-ons (dhcp server, weblet, ssh, whatever) as desired
>
good
> The new disk images could be the first LEAF releases, or could be called
> something else entirely. I'd like to avoid using EigerStein to prevent any
> confusion with the existing Eiger based distributions. These could also be
> the first images created by more than a single individual, so hopefully when
> something happens like one of us gets busy, work will not grind to a
> complete halt (like it has for me for about the last 3-4 months :< ).
>
> Does this seem like a good idea to anyone else?
>
it does :)
> Charles Steinkuehler
> http://lrp.steinkuehler.net
> http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
>
Eric wolzak
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
