From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do you keep up with system administration?
Date: Tue, 29 May 2007 07:32:15 -0700 [thread overview]
Message-ID: <9acccfe50705290732h81f98a5y9bf828c7a3d3adab@mail.gmail.com> (raw)
In-Reply-To: <d9a0a6da0705290701gad7635fka08a7b9ae103572f@mail.gmail.com>
On 5/29/07, Denis <denis.che@gmail.com> wrote:
> I'm curious to know your approach to keeping your Gentoo box current
> without it becoming a full-time job. I'm not talking about
> maintaining servers - just your "daily driver", so to say.
>
> How often do you sync with the current portage tree and compare it
> your versions in "world"? Should one do this once a week? Once in
> two weeks?
>
> How often to you update major components, like Xorg, kernel, and
> system tool chain? As soon as new things become available, or, say,
> once a month or so?
>
> The reason I ask is because I often don't have a lot of time to devote
> to system administration on a regular basis but do want to keep my box
> updated as much as possible. How do some of you non-developers
> balance system administration with your "day job"?
> --
> gentoo-user@gentoo.org mailing list
>
>
I have a cron job that does emerge --sync and another that does
revdep-rebuild -p. These email me their results.
At least once a week, I manually do
emerge -aDvu world
Unless there's something particularly weird, I say "yes" when
it asks if I want the emerge.
I have the PORTAGE_NICENESS set to 15 in /etc/make.conf,
and since there are 4 hyperthreads on this machine, I also have
MAKEOPTS=-j4. Together, these leave enough compute power
that I never really notice the load. Besides, it's easy to start the
emerge at the end of the day.
At the end of the emerge, I run etc-update. Each change I make
in a config file is tagged with a string that is easy to recognize.
If I have never modified a config file in the past, I accept all
changes -- I reason that if what the devs did the first time was
good enough, that is probably still true. There are only about
a dozen packages that I made any changes to, so it's fairly easy
to keep up with things.
Most weeks I spend less than an hour on administration.
--
Kevin O'Gorman, PhD
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-29 14:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 14:01 [gentoo-user] how do you keep up with system administration? Denis
2007-05-29 14:29 ` Mark Shields
2007-05-29 14:32 ` Kevin O'Gorman [this message]
2007-05-29 14:40 ` Ryan Sims
2007-05-29 14:48 ` Albert Hopkins
2007-05-29 14:50 ` Daniel Iliev
2007-05-29 16:49 ` Roy Wright
2007-05-29 17:07 ` Ralf Stephan
2007-05-29 17:39 ` Florian Philipp
2007-05-29 19:07 ` Denis
2007-05-29 18:45 ` kashani
2007-05-30 0:16 ` Tim Allinghan
2007-05-30 1:19 ` Denis
2007-05-30 2:20 ` Ryan Sims
2007-05-30 2:53 ` Michael Sullivan
2007-05-30 3:05 ` Denis
2007-05-30 7:21 ` Neil Bothwick
2007-05-30 9:06 ` Eray Aslan
2007-05-30 3:20 ` Kevin O'Gorman
2007-05-30 10:03 ` Benno Schulenberg
2007-05-30 17:20 ` Denis
2007-05-30 20:57 ` Neil Bothwick
2007-05-30 3:49 ` Boyd Stephen Smith Jr.
2007-05-30 4:37 ` Denis
2007-05-30 7:22 ` Neil Bothwick
2007-05-30 7:25 ` John covici
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=9acccfe50705290732h81f98a5y9bf828c7a3d3adab@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@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