public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Shields" <laebshade@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 10:29:59 -0400	[thread overview]
Message-ID: <642958cc0705290729v2efbfd73v7575c2e50d906fb6@mail.gmail.com> (raw)
In-Reply-To: <d9a0a6da0705290701gad7635fka08a7b9ae103572f@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

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 sync and do an emerge -DNpvu world daily.  The results are e-mailed to me
by vixie-cron.  This allows me to read what new packages are available and
also see the updates available.  These logs are sent to my gmail address
with a label and filter.  If I am so inclined I can view the current one or
past ones.  I can then log into the box and run emerge -DNavu world and
update, then run etc-update after that.  The only thing that's been bugging
me is restarting services after they've been updated (automagically, or
near-auto).

-- 
- Mark Shields

[-- Attachment #2: Type: text/html, Size: 1912 bytes --]

  reply	other threads:[~2007-05-29 14:39 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 [this message]
2007-05-29 14:32 ` Kevin O'Gorman
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=642958cc0705290729v2efbfd73v7575c2e50d906fb6@mail.gmail.com \
    --to=laebshade@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