From: Barry Shaw <baz@scms.waikato.ac.nz>
To: absinthe@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy for retirement of old gentoo 'versions'
Date: Mon, 05 Jul 2004 14:19:06 +1200 [thread overview]
Message-ID: <40E8BA9A.7010600@scms.waikato.ac.nz> (raw)
In-Reply-To: <200407042101.49322.absinthe@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dylan Carlson wrote:
| On Sunday 04 July 2004 6:16 pm, Barry Shaw wrote:
|
|>We've got about 250 machines currently gentooed,
|>with more to come, so we might be able to offer some insights into large
|>scale installations.
|
|
| Very nice. Yes, I would love to know more about how you're using Gentoo
| commercially.
|
Well we're a university, so we aren't commercial as such 8). All of the
machines are being installed via a custom script and a binary repository
that is used as a canonical source of packages. Additions and removals
are performed automatically each night on the clients. We've documented
the install process at http://www.scms.waikato.ac.nz/~baz and the
scripts are available there also. The nightly maintenance process and
scripts aren't yet published but its in the works. If you want a more
detailed description let me know and I can send you something offlist
(I'm not really sure this list is the right place for this kind of thing).
| In the past, I've done some production installs of FreeBSD with success,
| but not w/Linux yet. A Gentoo deployment should be more
controllable, in
| my estimation, than FreeBSD, but there's a lot of work to be done on both
| to make them more sane for commercial environments. IMO, the first
| priority is just minimizing the rate/amt of change. That's half the
| battle. IT folks can't be burdened with the minutae of researching &
| testing lots of tiny little package updates.
|
| The "don't rsync" solution is a kludge... we need something a tad more
| thoughtful, functional than that. :-)
|
Definitely, thats where I see a stable portage tree as being very useful.
| If you don't mind my asking, how many of your Gentoo machines are
| workstations? Servers? What kind of work is done on these machines?
|
Most of them are workstations, both lab machines and staff and graduate
desktops (they are all maintained in a similar fashion). We've only got
a few gentoo servers, mainly since we only started using gentoo here
less than 6 months ago and we're only upgrading the servers as they are
replaced (if it aint broke.....).
Baz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFA6LqaJvZkjpKMF2wRAkNVAKCKd88s/qUPlQPTquiCsS1VhJNJ7gCfUzHH
IR/4zWK9bMVyWcBLw9OtGrA=
=LYLd
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-05 2:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 1:20 [gentoo-dev] Policy for retirement of old gentoo "versions" Barry Shaw
2004-07-02 2:17 ` [gentoo-dev] Policy for retirement of old gentoo 'versions' Donnie Berkholz
2004-07-02 12:48 ` Chris Gianelloni
2004-07-02 13:44 ` William Kenworthy
2004-07-02 14:41 ` Grant Goodyear
2004-07-02 15:15 ` Dylan Carlson
2004-07-02 20:29 ` Chris Gianelloni
2004-07-02 21:06 ` Dylan Carlson
2004-07-02 21:37 ` Chris Gianelloni
2004-07-03 6:34 ` Dylan Carlson
2004-07-04 22:10 ` Marius Mauch
2004-07-05 1:14 ` Dylan Carlson
2004-07-04 22:16 ` Barry Shaw
2004-07-05 1:01 ` Dylan Carlson
2004-07-05 2:19 ` Barry Shaw [this message]
2004-07-02 20:21 ` Chris Gianelloni
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=40E8BA9A.7010600@scms.waikato.ac.nz \
--to=baz@scms.waikato.ac.nz \
--cc=absinthe@gentoo.org \
--cc=gentoo-dev@lists.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