The obvious, I guess - never touch a running system. People who have a working Bering system would not have to worry about some new version. I can surely understand that people don't want to constantly mess with their firewalls (especially if it took some work to get everything just right), so being able to support the systems that are around would surely be a plus.What would be the advantage and drawbacks of keeping the Bering & Bering-uclibc distributions separate ?
Having said that, to me, Bering uClibc seems like the only way to go - simply because glibc 2.0 is no longer receiving any updates, and it's just a matter of time until things will just not work with it anymore (just look at the mess NPTL has caused with "legacy" applications on the newer RedHat systems) - especially with kernel 2.6 being out, it's bound to happen that things will move on, and applications will rely on the newer infrastructure (which glibc 2.0 cannot accomodate).
I've looked at newer glibc versions, and they just won't work for a floppy (at least for a simple guy like me :-)). And while I may not need to run things from a floppy (all my leaf boxes run either from CD or CF), being able to boot from one or two floppy/floppies is still something that makes leaf very special - if one removes that, there are a ton of alternatives (Linux or BSD based) that will do the job just fine.
What about the possability of moving forward with a mixed approach for the next major version?
The core system (and most packages) could be compiled against uClibc, while packages that require it are compiled against a newer glibc that would optionally be installed by those with enough room (ie: running from HDD/flash/CD-ROM/etc).
-- Charles Steinkuehler [EMAIL PROTECTED]
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
