From: Roy Wright <royw@cisco.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do you keep up with system administration?
Date: Tue, 29 May 2007 11:49:45 -0500 [thread overview]
Message-ID: <465C59A9.9080505@cisco.com> (raw)
In-Reply-To: <20070529145013.BF6858B3B8@mail.ilievnet.com>
Daniel Iliev wrote:
> I have a daily cron job containing:
> ===
> emerge --sync && \
> emerge -DuNf world && \
> glsa-check -t all 2>&1 | mail -s "GLSA report" root
> ===
>
> In other words it syncs the tree, fetches all the new packages and then
> checks for security vulnerabilities. If glsa-chack says "This system is
> not affected by any of the listed GLSAs" I update when I have the time
> (mostly in the weekends), otherwise I update ASAP.
>
>
In addition to the above, my cron job also syncs my overlays, updates
eix database,
checks dependencies, and verifies nvidia driver was not updated behind
my back :-)
echo "Syncing overlays..."
/usr/bin/svn cleanup /usr/portage/local/layman/xeffects
layman -S
echo "Running update-eix..."
update-eix --quiet
echo "Running revdep-rebuild"
revdep-rebuild --ignore --pretend --no-color
rm -f /.revdep-rebuild.*
echo "show openGL selection"
eselect --no-color opengl list
So my daily routine is to check the email from cron, then as long as nothing
big needs to be updated, run emerge -uDNav where I examine the use flags,
particularly the not selected ones. For big updates like kde and gcc, I
wait
for the weekend then check for any updating issues (b.g.o., forums, this
list).
HTH,
Roy
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-29 16: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 [this message]
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=465C59A9.9080505@cisco.com \
--to=royw@cisco.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