public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do you keep up with system administration?
Date: Tue, 29 May 2007 22:49:25 -0500	[thread overview]
Message-ID: <200705292249.30118.bss03@volumehost.net> (raw)
In-Reply-To: <d9a0a6da0705290701gad7635fka08a7b9ae103572f@mail.gmail.com>

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

On Tuesday 29 May 2007 09:01:39 Denis 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.

In server-land I would perform all upgrades on a test system before rolling to 
production anyway.

> How often do you sync with the current portage tree and compare it
> your versions in "world"?

I sync, update system and world, and then revdep-rebuild daily.  I run ~amd64.
Unfortunately, this can get you into some sticky situations: my pdns still 
doesn't like my new postgres.

If you are running stable, it's much less likely to result in bad situations, 
and you should be able to put off upgrades much longer.  A daily (or weekly) 
sync is still a good idea IMHO; having an up-to-date tree is rarely a 
disadvantage.

> How often to you update major components, like Xorg, kernel, and
> system tool chain?

I live on the edge and treat them like any other package.  Well, 'cept the 
kernel, which I only actually compile and reboot into occasionally.  If you 
don't have time to wrestle with issues, but off the upgrade.  Nothing sucks 
worse than not having the time to fix X, but needing it to work/play and 
having to broken.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-05-30  3:55 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
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. [this message]
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=200705292249.30118.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --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