From: Brett Johnson <brett@blzj.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] backups and world updates
Date: Thu, 28 Jul 2005 09:11:09 -0500 [thread overview]
Message-ID: <42E8E77D.9050308@blzj.com> (raw)
In-Reply-To: <1f81f7e005072806534ed43866@mail.gmail.com>
Mark wrote:
> Thanks to everyone who helped me get my system back after a couple of
> world update snafus. Now of course I'm a little gun-shy about using
> options like emerge --update world. So what's my best bet to keep my
> system up to date, while protecting it from my own lack of
> understanding of updating config files?
>
> Here's what I'm intending to do so far:
>
> 1. Prior to running any large system update, back up /etc to another location
> 2. use dispatch-conf instead of etc-update
>
> Can anyone make any other suggestions? Which emerge options are best
> for full system updates? Thanks
I would suggest doing updates on a very regular basis. I saw a script in
the gentoo forums once, where the script ran every night and updated the
portage tree, downloaded and built all the new packages (but not install
them) and emailed the list of packages to be installed. I have not
gotten that ambitious yet, I just update my portage tree every night,
and try run an "emerge -puvD world" once a week on all my systems to see
what needs to be updated. If you stay on top of updates, they are much
easier to handle. (I know this because I have neglected my laptop for
about 6 months now, and now I have been stuck updating it for the past 2
days....)
I have also found that using dispatch-conf with rcs and colordiff helps
a lot too. http://gentoo-wiki.com/TIP_Colorized_Config_Management shows
how to colorize the diff for etc-update and dispatch.conf.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-28 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 13:53 [gentoo-amd64] backups and world updates Mark
2005-07-28 14:11 ` Brett Johnson [this message]
2005-07-31 3:48 ` [gentoo-amd64] emerge of neverwinter nights fails Mark Creamer
2005-07-31 3:57 ` shimi
2005-07-31 9:24 ` Michal Žeravík
2005-07-31 9:51 ` Peter Humphrey
2005-07-31 17:05 ` phil
2005-07-31 21:39 ` Michal Žeravík
2005-07-31 23:05 ` Mark Creamer
2005-08-01 15:59 ` Chuck Milam
2005-08-01 16:11 ` Peter Humphrey
2005-08-01 17:10 ` Chuck Milam
2005-08-01 20:10 ` phil
2005-08-01 18:49 ` phil
2005-07-31 9:25 ` [gentoo-amd64] " Duncan
2005-07-28 14:22 ` [gentoo-amd64] backups and world updates Roy Wright
2005-07-28 15:13 ` Mark
2005-07-28 18:32 ` Roy Wright
2005-07-28 15:47 ` Matt Randolph
2005-07-28 15:15 ` Matt Randolph
2005-07-29 14:25 ` [gentoo-amd64] " Duncan
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=42E8E77D.9050308@blzj.com \
--to=brett@blzj.com \
--cc=gentoo-amd64@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