> Charles,
> What can we do to help you get the new release finished?
Come to KS and help me unpack my office, pack my personal belonging, and
move into my new house. ;-)
Actually, there's quite a bit that can be done...from trolling the list
archives:
> - The distribution needs a name...again, I'd prefer Ewald to name it,
since
> he's been doing all the work
The name is Dachstein. PROGRESS!!!
> - 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...
> - The readme file needs to be updated with (at minimum) new links and new
> instructions for e3 rather than ae as the editor
> - The readme instructions need to be verified (ie put on LUser hat & walk
> through the readme like a newbie, making sure nothing unexpected happens).
>
> And on to 'real' changes required/desired:
>
> - I'd like to see the java bandwidth applet added to the weblet package
> - 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
> - 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.
> - Remove old dhcpd and dhclient leases...that these are around is my
fault,
> as they are getting backed up with root. I need to add an exclude.list
file
> to each package.
> - Modify the dhclient.conf file to properly generate an /etc/resolv.conf
> that uses the local dnscache
> - 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. I'd like to see future images use
> seawall, rcf, or similar.
I've got work done on the dhcpd/dhclient pacakges, and using the ramlog
package instead of log...as long as I can find my test disks (they're in a
box somewhere), these are done.
I'm likely the only one to modify the networking scripts, as I've got to
fold together pieces of 3 different scripts into a unified whole.
Stuff someone other than me can work on:
Go back to using ctar to create the LRP files when backing up. I ran into
problems archiving root.lrp when using the new scripts. Ctar is small
enough, and package archiving is important enough, I'd like to leave it
'as-is' in this release.
Verifying the dnscache configuration. While I was previously thinking using
daemontools would be a good thing, recent threads on the licensing have made
me change my mind...
Updating the weblet package
Updating the syslinux splash screen
Updating the readme file
There's probably more stuff, but this is what comes immediately to mind...
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
