public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System maintenance procedure?
Date: Sat, 08 Dec 2012 17:20:36 -0600	[thread overview]
Message-ID: <50C3CB44.7070307@gmail.com> (raw)
In-Reply-To: <20121208224950.40759f8e@digimed.co.uk>

Neil Bothwick wrote:
> On Sat, 8 Dec 2012 13:54:25 -0800, Grant wrote:
>
>> Got it.  So @preserved-rebuild is meant to be a replacement for
>> revdep-rebuild
> No, it is a means of preventing the problems that revdep-rebuild fixes.
>
> If revdep-rebuild were a medicine, @preserved-rebuild would be a vaccine.
>
> Which you choose to use depends on whether you prefer fixing broken
> systems to avoiding them.
>
> revdep-rebuild is an external program created to deal with a shortcoming
> in emerge, that shortcoming was the lack of @preserved-rebuild. There may
> be times when @preserved-rebuild fails, although they are becoming
> increasingly rare, so revdep-rebuild is still useful as a fallback, but
> the main reason I run it from my weekly system check script is as a
> sanity check. It rarely finds anything.
>
>


That's been my experience too.  I run @preserved-rebuild when it tells
me to but revdep-rebuild rarely finds anything.  Thing is, it has a time
or two.  It is best to run revdep-rebuild and be sure than not to and
run the risk of not being able to boot or some other problem that bites
you. 

Sort of like a ounce of prevention is worth a pound of cure.  ;-) 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!



  reply	other threads:[~2012-12-08 23:22 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  0:30 [gentoo-user] System maintenance procedure? Grant
2012-12-05  1:00 ` nybblenybblebyte
2012-12-05  1:21 ` Dale
2012-12-05  3:55   ` Grant
2012-12-05  1:36 ` Neil Bothwick
2012-12-05  4:04   ` Grant
2012-12-05  4:34     ` Dale
2012-12-05  5:15       ` Grant
2012-12-05 10:22         ` Dale
2012-12-08  0:57           ` Grant
2012-12-08 22:04       ` Grant
2012-12-08 23:25         ` Dale
2012-12-15  3:38         ` Grant
2012-12-05 12:50     ` Neil Bothwick
2012-12-08  0:55       ` Grant
2012-12-05  3:15 ` Pandu Poluan
2012-12-05  3:29   ` Allan Gottlieb
2012-12-05  3:34   ` Dale
2012-12-05 10:05 ` Alan McKinnon
2012-12-08  0:56   ` Grant
2012-12-08 11:58     ` Neil Bothwick
2012-12-08 20:06     ` Alan McKinnon
2012-12-08 21:07       ` Grant
2012-12-08 21:25         ` Alan McKinnon
2012-12-08 21:54           ` Grant
2012-12-08 22:08             ` Alan McKinnon
2012-12-09  0:41               ` Grant
2012-12-08 22:49             ` Neil Bothwick
2012-12-08 23:20               ` Dale [this message]
2012-12-09  4:22                 ` Dale
2012-12-09 13:18                 ` Bruce Hill
2012-12-09 16:48                   ` Neil Bothwick
2012-12-09 17:01                     ` Bruce Hill
2012-12-09 19:06                       ` Neil Bothwick
2012-12-11 13:36                     ` Bruce Hill
2012-12-11 14:04                       ` Neil Bothwick
2012-12-11 17:20                       ` Michael Orlitzky
2012-12-12  6:05                       ` Alan McKinnon
2012-12-12  9:29                         ` Neil Bothwick
2012-12-12 15:10                         ` Bruce Hill
2012-12-12  9:49                       ` Neil Bothwick
2012-12-12 12:16                         ` design [depois das dez]
2012-12-09  0:33               ` Peter Humphrey
2012-12-10  7:50 ` Daniel Wagener
2012-12-10  8:41 ` [gentoo-user] " Steven J. Long

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=50C3CB44.7070307@gmail.com \
    --to=rdalek1967@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