public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Teresa and Dale <teendale@vista-express.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] etc-update
Date: Mon, 26 Jun 2006 10:59:09 -0500	[thread overview]
Message-ID: <44A0044D.6000601@vista-express.com> (raw)
In-Reply-To: <342e1090606260753o6f93c129x8a50782c622ea6d1@mail.gmail.com>

Daniel da Veiga wrote:

> On 6/26/06, Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
>
>> On Monday 26 June 2006 14:36, Sean wrote:
>> > What is the best way to handle the files that etc-update states
>> needs to
>> > be updated?
>>
>> There are three competing utilities for this purpose. The official
>> etc-update
>> (which sucks and should have been deprecated a long time ago... ;) ),
>> dispatch-conf and cfg-update.
>>
>
> What's the matter with etc-update? It just does it all...
>
>> > It displays a list of all the files that need updating, but does it
>> > actually put this list into a file anywhere so that I can manually
>> look
>> > them over to see what the differences are?
>>
>> This will show the new files:
>>
>> # find /etc -name ._cfg*
>>
>> > Or could anyone suggest the best steps to proceed?
>>
>> What you should do is figure out how to use either dispatch-conf or
>> cfg-update. Personally I use dispatch-conf because I learned that
>> first and
>> it satisfies my needs. I think cfg-update is superior but never
>> bothered to
>> investigate. A couple of references:
>>
>> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4
>> http://forums.gentoo.org/viewtopic.php?t=86622
>>
>
> I don't see why use other tool. Etc-update works great...
> I've been using it since my first Gentoo install 2 years ago and never
> needed (neither bothered looking for) this other tools you mentioned.
>

I have tried the other tools and they are not any better.  The biggest
thing, no matter what tool you use, is to be VERY careful what you
update.  For me, about 95% of the stuff is fine but that 5% can keel you
or make you wish you were dead.  O_O

Dale
:-)  :-)
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-06-26 16:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 12:36 [gentoo-user] etc-update Sean
2006-06-26 12:53 ` Bo Ørsted Andresen
2006-06-26 14:24   ` Alexander Skwar
2006-06-26 14:38     ` Bo Ørsted Andresen
2006-06-26 17:33       ` Alexander Skwar
2006-06-28  7:40       ` Daevid Vincent
2006-06-29 21:46         ` Tamas Sarga
2006-06-26 14:29   ` A. Khattri
2006-06-26 14:43     ` Bo Ørsted Andresen
2006-06-26 17:28       ` A. Khattri
2006-06-26 17:35         ` Bo Ørsted Andresen
2006-06-26 17:35     ` Alexander Skwar
2006-06-29 16:08       ` A. Khattri
2006-06-26 14:53   ` Daniel da Veiga
2006-06-26 15:59     ` Teresa and Dale [this message]
2006-06-26 16:29       ` Neil Bothwick
2006-06-26 17:07         ` Teresa and Dale
2006-06-26 17:30           ` A. Khattri
2006-06-26 18:17             ` Teresa and Dale
2006-06-26 23:40     ` David Corbin
2006-06-29 16:09       ` A. Khattri
2006-06-29 16:38         ` Gerhard Hoogterp
2006-06-29 17:21           ` Neil Bothwick
2006-07-02  9:43           ` Alexander Skwar
2006-06-29 21:42         ` David Corbin
2006-06-29 21:53           ` Bo Ørsted Andresen
2006-06-26 14:18 ` Alexander Skwar
2006-06-26 18:41 ` Philip Webb
2006-06-29 16:11   ` A. Khattri
2006-06-26 20:20 ` leszek

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=44A0044D.6000601@vista-express.com \
    --to=teendale@vista-express.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