From: "Brett Simpson" <Simpsonb@hillsboroughcounty.org>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Gentoo for production servers.
Date: Fri, 05 Dec 2003 14:38:15 -0500 [thread overview]
Message-ID: <sfd0985b.077@GroupWise> (raw)
This quote was made by Daniel Robbins in an OSNews article. http://www.osnews.com/story.php?news_id=1080
"Gentoo Linux is currently a "bleeding-edge" type distro. It makes Gentoo Linux the ideal distribution for hobbyists who get lots of cool toys before everyone else, but makes Gentoo Linux a questionable choice for production server environments,"
"We're going to take pieces of the current "bleeding-edge" Gentoo Linux meta-distribution, refined them and use them as the basis for a robust, well-maintained version of Gentoo Linux -- geared exclusively for servers. For this project, we will reduce the number of ebuilds in our server branch from 1800 to around 400, at least initially. Our stable CVS tree will be completely separate from our current bleeding-edge version -- a "code firewall", if you will. Commit access will be limited to an elite team of Gentoo Linux developers. We will lock down upgrades so that "emerge --update world" will only fix known bugs and security fixes. Each release of this new server meta-distribution will have an official one-year lifespan, during which it will be painstakingly maintained by us. In-place upgrades to new releases will be fully-tested and very smooth. We will have some cross-pollination with our current tree, but anything that goes into the server distro will be carefully audited before being added. We are still developing the goals for our new server project, but based on feedback from the rest of our development team (who seem to be in near unanimous agreement) it looks like the project will progress very closely if not identically to how it is described above."
Since this was based off of Gentoo 1.0 how relevant is this for the current 1.4 release in a production server environment?
Thanks,
Brett
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-12-05 19:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 19:38 Brett Simpson [this message]
2003-12-05 19:51 ` [gentoo-dev] Gentoo for production servers Lisa Seelye
2003-12-05 20:10 ` Brett Simpson
2003-12-05 20:34 ` Brett Simpson
2003-12-05 20:45 ` Jon Portnoy
2003-12-05 21:33 ` Don Seiler
2003-12-05 22:34 ` Mike Williams
2003-12-06 3:20 ` Don Seiler
2003-12-06 3:34 ` Corey Shields
2003-12-06 3:30 ` Corey Shields
2003-12-07 10:45 ` Paul de Vrieze
2003-12-07 18:36 ` Lisa Seelye
2003-12-07 19:11 ` Paul de Vrieze
2003-12-08 18:25 ` david
2003-12-08 19:30 ` Lance Albertson
2003-12-07 20:15 ` Jeff Smelser
2003-12-16 22:13 ` Paul de Vrieze
2003-12-06 12:16 ` Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sfd0985b.077@GroupWise \
--to=simpsonb@hillsboroughcounty.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox