> >- The distribution needs a name...again, I'd prefer Ewald to name it,
since
> >he's been doing all the work
> >
> I have 2 options in mind. The first one is "Dachstein", which is a
> mountain in the Hohe Tauern (Austria iirc). This would make a more or
> less obvious connection to Eigerstein. The other one is "Alpamayo"
> (Cordillera Blanca, Peru) which is considered one of (if not the-) the
> most beautiful mountains on earth by many. I tend to favor Dachstein a
> little. Any opinions?
Either name would be fine...
> >- The syslinux splash screen should be changed. It should probably refer
to
> >the leaf sourceforge project. We may also want to pull the links to
> >linuxrouter.org, but I'm not sure about this...
> >
> That was more or less on my todo list. Perhaps pull the links to
> linuxrouter and put them in the readme.txt. And if we want to waste
> disk-space we can add a graphical splash-screen! (.e.g with the leaf-logo)
I like the idea of just a link to leaf.sourceforge.net on the syslinux
splash screen, with other links in the readme.
> >- The readme instructions need to be verified (ie put on LUser hat & walk
> >through the readme like a newbie, making sure nothing unexpected
happens).
> >
> I'll ask a friend to do a beta test, or perhaps my parents :-)
I usually do this with the self-extracting disk images just before I release
them...I can do a pretty good job of 'playing dumb'.
> >And on to 'real' changes required/desired:
> >
> >- I'd like to see the java bandwidth applet added to the weblet package
> >
> OK, what about Justin Ribiero's modifications George Metz mentions on
> his pages? I haven't tried these though.
I'll try to dig these mods up...
> >- I'd like dnscache to be run by the daemontools package, if it doesn't
> >require too much disk space...this should help keep things standardized,
and
> >make tinydns package maintainence easier
> >
> Good, I agree.
>
> >
> >- Use the ramlog package instead of the log package...this puts the logs
on
> >a seperate ramdisk, avoiding the full ramdisk issues, which are the most
> >likely thing to kill a working LRP system.
> >
> This was on my todo list for another release, as well as support for
> loading kernel modules from linuxrc. What do people think about that
> last point?
I missed loading kernel modules from linuxrc. I think this should be on the
to-do list, as it won't add much (if any) to the size of root.lrp, and will
make life easier for the handful of folks wanting to run off HDD, zip, or
other non-floppy media.
> >- Update the network scripts...I need to fold my proxy-arp and Extended
> >scripts V1.1 together and create what will likely be the last of the
> >'mountain' firewall script derivations.
> >
> If I understand the description of the 1.1 scripts on
> lrp.steinkuehler.net correctly these are an extension of the 1.0
> scripts, and incoporate all of the 1.0 features? Before I was worried
> about 1.1 not supporting port-forwarded dmz servers.
The scripts will be a clean extension of the existing Eiger firewall
scripts, so any existing Eiger based network.conf would work properly. The
extensions will allow alternate forms of DMZ support (port-forwarded,
static-NAT, or proxy-arp based) in addition to the standard routed DMZ
supported by the Eiger scripts currently.
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
