On Wednesday 21 January 2004 04:00, Warren Togami wrote:
https://bugzilla.fedora.us/show_bug.cgi?id=163 The libsafe package needs fixing if Legacy wants to use it. It must remain the old fedora.us-style package naming in order to not conflict with fedora.us' libsafe.
Thoughts?
I personally don't like the idea of more addons for legacy systems. The goal has been to change as little as possible. Starting an addon trend may wind up getting us inundated with requests to add this, or update that. I do think that it would fit in with Fedora.us, although you've stated that you didn't want to do extras for the older releases.
libsafe I am suggesting as a special case NOT for the legacy-utils repository, but for advanced users on the web page only. It is not suitable for a fire-and-forget solution and must be monitored for a while.
My earlier post suggested a very short list of extremely simple, yet useful add-ons for typical servers for the legacy-utils repository. legacy-utils add-on packages are only by consensus and can easily be shot down. This is the list of add-ons that I am proposing:
bonnie++ Very useful stability test for servers chkrootkit Security checking for servers ddrescue Data recovery for servers hardlink Space consolidation for mirror servers iptstate Very simple Netfilter stateful top *
I suppose I'll leave it up to the community to see if anybody would be interested in seeing this show up on the page, but frankly, we've got enough to do w/out adding optional packages to the mix. There are plenty of packages to QA and a few updates-testing to test and get ready for full release.
You make a good point about 'plenty of other work to do', but in this case libsafe is already well tested and unchanged for almost a year.
The only real reason I can see for not putting it somewhere on the Legacy webpage is if people find serious functionality regressions caused by libsafe on these distributions. I personally am not aware of any now, but I invite others post reproduction procedures here.
* Might be unstable due to an old ncurses bug. Needs extensive testing before inclusion. Probably just kill this from the list to be on the safe side.
Warren
