> * Updated glibc
> * Updated linux (to 2.4 series)
> * New and improved configuration files
> * Bootable CDROM (using standard floppy image)
> * Build a LRP diskette menu-by-menu
> * Removal of multicron
Certainly more add on packages, and a central repository for them. If we go
with glibc2.1 or 2.2 we'll need a way to keep the old packages separate from
the new ones, like a new extension or something.
Perhaps a move to fat32 on the floppy so that we can use long file names on
floppies to more easily version packages, etc. Can syslinux support fat32?
When we move to linux 2.4, I believe we should look into using perhaps tmpfs
or another low overhead file system format other than minix for the ram disk
partitions.
Different Busybox packages with different applets included so that people
can get as much or as little as they want, depending on what they plan on
doing with their box.
Security auditing, every new version should make sure it as least as secure
as the last, and whenever a security fix comes out for a package that a
number of people use lrp with, a security alert and a new package should be
sent out to the major lists. Perhaps even a separate mailing list just for
security issues.
Documentation, while the documentation available is good, it doesn't take
long to get out of date, and many of the Leaf projects documents are out of
date. Many more have yet to be even written.
That's just my quick thoughts, I'm sure there are many other ideas on what
could be different or better in future releases, and with LEAF in general.
Andrew Hoying
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
