From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update
Date: Sat, 28 May 2011 11:05:17 -0500 [thread overview]
Message-ID: <4DE11D3D.1050208@gmail.com> (raw)
In-Reply-To: <4DE11C24.7080707@libertytrek.org>
Tanstaafl wrote:
> Hello,
>
> Ok, I'm about to do the deed, but was concerned about one thing...
>
> The migration guide only mentions using dispatch-conf after performing
> the update...
>
> I have only/always used etc-update for all the years I've been using
> gentoo, and would really, REALLY prefer not to use a new/unfamiliar tool
> during a procedure like this on a production server.
>
> I'm hoping that this was just a minor oversight, and that etc-update is
> fully supported as pr migration?
>
>
>
I used etc-update for mine and it went well. I think that just shows
the person writing the guide uses dispatch-conf.
Dale
:-) :-)
next prev parent reply other threads:[~2011-05-28 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 16:00 [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update Tanstaafl
2011-05-28 16:05 ` Dale [this message]
2011-05-28 16:07 ` Bill Longman
2011-05-29 9:07 ` Jake Moe
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=4DE11D3D.1050208@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