Gentoo ... I still prefer Slackware, my order would be:
1. Slackware 2. Debian 3. Open/Free BSD
I doubt that the Slackware community would let it slip away.
Michael.
Travis Rousseau wrote:
Yes this is a Major thing! If this would have been asked before he got sick i would have said just Slackware but now I say Debian first then Slackware second he does have people to carry the distros if something does happen to him _But_ I don't know if they would just support it for a few years and wonder of or if they would take command and they will take his place. Because of this I have switched my #2 server to Debian (#1 runs RHEL3 :( ) from Slackware. But Slackware is still in my top 3 favorite Distros 1.Gentoo 2.Debian 3.Slackware
I will recommend Gentoo once http://www.gentoo.org/proj/en/glep/glep-0019.txt makes enough progress (Doesn't look like it though :( )
Travis R.
An honest question - since I can't profess to be an expert on Slackware: how comfortable are you (and other Slackware experts) with the distros' survivability, if something should happen to its chief maintainer? From what I had read, there was a recent rather serious health scare (fortunately seems ok now) - so this issue can become very real in a hurry ...
I'm asking the question, since for an enterprise situation without considerable inhouse expertise, you'd really hate to be stuck with a strategic tool to your infrastructure, if that tool would seriously suffer from the absence of a single individual. Of course, if you have significant inhouse expertise, the hop to a different distro isn't as dramatic as hopping between operating systems or even hopping between various flavours of Unix.
...Niels
Michael Gale wrote:
Hello,
I agree with Travis, Debian or Slackware make a enterprise distro. I my self am a big Slackware fan.
Michael.
Travis Rousseau wrote:
Ok sorry but the DVD Novell sent me was a dud :( just won't work!
I would recommend Debian woody or Slackware for enterprise "like" situations or where you need low maintenance equipment and want stability but dont need really good support (In my opinion google can provide some of the best support just by googling the errors)
I use Suse 9.2 and the like for more desktop situations where stability is not as critical (In my opinion)
Travis R.
Travis Rousseau wrote:
Well for Redhat I have one RHEL3 server and a few RH9 and FC3 computers. From them there is a few main differences the first is support for RHEL Redhat provides support right to you. For FC3 you find what support you can (You'll find it for everything!). The second main difference is your not using release packages (or at least me) with RHEL3 your using old packages with security fixes back ported to older "Known to be fully stable". Now with fedora core you get the packages at release time and they have undergone little if any testing so you do not know how well it will react in the situation it is put in and you must worry about package discrepancys.
I will install a Suse Enterprise server 9 from novell right now and report back the diffrences for suse.
Travis R.
Shawn wrote:
I have a contact who is considering an enterprise Linux solution, but I don't think he really needs one. Before I give him my "formal" opinion, I thought I'd ask what the difference is between a regular desktop version and the enterprise version of Linux. (say Suse Pro vs Suse Enterprise)
As I understand things (and freely admit I could be wrong), there is no difference other than the bundled support contract with the Enterprise edition. Is this correct? Or are there other differences in terms of available packages or the "quality" of the packages?
Thanks for any input.
Shawn
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
