* [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update
@ 2011-05-28 16:00 Tanstaafl
2011-05-28 16:05 ` Dale
2011-05-28 16:07 ` Bill Longman
0 siblings, 2 replies; 4+ messages in thread
From: Tanstaafl @ 2011-05-28 16:00 UTC (permalink / raw
To: gentoo-user
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update
2011-05-28 16:00 [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update Tanstaafl
@ 2011-05-28 16:05 ` Dale
2011-05-28 16:07 ` Bill Longman
1 sibling, 0 replies; 4+ messages in thread
From: Dale @ 2011-05-28 16:05 UTC (permalink / raw
To: gentoo-user
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
:-) :-)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update
2011-05-28 16:00 [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update Tanstaafl
2011-05-28 16:05 ` Dale
@ 2011-05-28 16:07 ` Bill Longman
2011-05-29 9:07 ` Jake Moe
1 sibling, 1 reply; 4+ messages in thread
From: Bill Longman @ 2011-05-28 16:07 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 78 bytes --]
Yes, absolutely. I use cfgupdate too.
--
Bill Longman
Sent from my Galaxy S
[-- Attachment #2: Type: text/html, Size: 99 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update
2011-05-28 16:07 ` Bill Longman
@ 2011-05-29 9:07 ` Jake Moe
0 siblings, 0 replies; 4+ messages in thread
From: Jake Moe @ 2011-05-29 9:07 UTC (permalink / raw
To: gentoo-user
On 05/29/11 02:07, Bill Longman wrote:
>
> Yes, absolutely. I use cfgupdate too.
>
> --
> Bill Longman
> Sent from my Galaxy S
>
There was an announcement on the gentoo-announce mailing list that
listed a few different docs for reference. Among other things, the part
of interest in this discussion was:
After these packages are emerged, it is absolutely critical that you
immediately update your configuration files with dispatch-conf,
etc-update or a similar tool [2] then follow the steps in the OpenRC
Migration Guide [3].
2. http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=4
3. http://www.gentoo.org/doc/en/openrc-migration.xml
Like Dale, I used etc-update, and on two different laptops (one x86 and
one amd64), which worked without hitch on both.
Jake Moe
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-05-29 9:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-28 16:00 [gentoo-user] Baselayout2/OpenRC migration question - dispatch-conf vs etc-update Tanstaafl
2011-05-28 16:05 ` Dale
2011-05-28 16:07 ` Bill Longman
2011-05-29 9:07 ` Jake Moe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox