-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlo Florendo wrote:
> As is obvious from your previous years' post, you are very bitter. Really > bitter at leaving Comodo. If you can't say anything nice, may I > respectfully request you to please shut up. You are not doing anything > constructive to this list nor to TSL. You may have contributed to TSL > before but that was before. Since you've got nothing, and absolutely > nothing to do with TSL now, you've got no right to brag about your being > the author of swup nor about anything you've done to TSL. He's just speaking his mind, so what? He has some very good points, and instead of attacking him maybe you could come up with some arguments of your own about what he (and I for that matter) say... The fact is that TSL 2.2 is _way_ old. Modern (current) hardware is getting more and more difficult to run with TSL. Most of the TSL users are running an (inofficial) 2.6 kernel on it to get it to work at all. Most of the packages from TSL 2.2 suffer the same aging problem as the kernel does. Don't read this as a rant - its just the truth. And its no ones fault - TSL is just showing its age. And there is no point in denying that the stable TSL 3 version is overdue. Or that there is just one guy left keeping it running. I worked in a company once which used an inhouse distro, so I think i know the Nived job. If you're just one guy having to read all the security lists, keeping track of all packages, backporting fixes to your anciend program versions, verifying if your versions are vulnerable at all etc - you just don't have time left for anything else. Same goes for the super secret guy developing the new stuff. Back in the good times if there was any TSL related problem all it took was a mail or a irc query, and you got a fix instantly. Now major parts of the distribution system can break for more than a week and no one notices (as stated on the list before... several times...) Go figure. Again, no offense ment - the day has just 24 hours, and Nived wants to go home once in a while :-) So, whats the point in choosing TSL for new systems anyway? Christian made some very good points about that before. I realize that there are some, but very few... And all of them are void if you take just a peek at for example CentOS and see how much of your knowledge you can use there, and how easy the transition is... There are just three things that made TSL special back in the old days... 1. Swup. A really great tool back then, better than anything else for software management (with RPMs) 2. Small footprint. The last remaining TSL box i'm responsible for is a 486-200 with 48 MB Ram. 3. "short ways" to contact the developers, and fast solutions to problems Whats left of that today? 1. There is yum for example. Does everything swup does, but is faster, better supported and more reliable. 2. You can get other distros to run on that too, though it might involve more work (eg. removing some parts you dont need and which TSL simply didnt install in the first place). With kickstart or similiar tools you can automate that very good, making this point invalid from todays point of view too 3. Well, just read the list :-) I migrated a TSL based appliance to CentOS in a matter of days. A very small number of days. Including internal install servers, rewriting all scripts from swup-usage to yum etc. It's really easy, just a handfull of "chkconfig foobar off" and "rpm -e foobar" lines in the kickstart file and you're set. Migrating running servers is more complicated, but as i said, TSL 2.2 systems are showing their age everywhere, so it might be a good idea to think about new hardware, or a reinstall anyhow... Danny - -- There is infinite time. = http://www.cyberdelia.de You are finite. = [EMAIL PROTECTED] Zathras is finite. = This is wrong tool. = \o/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGy8FjCa/LtJGgW5ERAlSiAJ4tODIRQyIF+N8jCq9o5IQ4ijyP4QCcCV4d SUZEzVI2aG8rSHOaABTCfpY= =KlBo -----END PGP SIGNATURE----- _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
