Date: Sun, 6 Nov 2022 21:07:16 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-current@freebsd.org Subject: Re: Seeking an idiot's guide to etcupdate/mergemaster Message-ID: <20221106210716.1c997091ca40ea02ede9f159@dec.sakura.ne.jp> In-Reply-To: <20221106031204.GA45827@www.zefox.net> References: <DC32CA76-5072-4521-BCD8-CDF1512420D4@yahoo.com> <20221021175142.GA62386@www.zefox.net> <B90AA192-17B4-4FE3-8050-1E7889432ED4@yahoo.com> <0697DE1F-C626-4289-894A-4141CDF1B91B@yahoo.com> <71AB9FAC-EB00-48F0-B0DD-0629C2D3C8C0@googlemail.com> <5719632F-8A92-4784-88D8-EAE3F20F2FA3@yahoo.com> <20221024174930.GA79381@www.zefox.net> <DBA8B2E1-D596-4664-A6F3-893C43265317@yahoo.com> <20221025005012.GA80394@www.zefox.net> <605A6723-5D31-495C-8200-FD107115FC81@yahoo.com> <20221106031204.GA45827@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 5 Nov 2022 20:12:04 -0700 bob prohaska <fbsd@www.zefox.net> wrote: > On Mon, Oct 24, 2022 at 08:32:17PM -0700, Mark Millard wrote: > > > > Your /etc/rc.d/ldconfig script seems to have not been updated > > by use of etcupdate or mergemaster or other such. (How much > > else is also out of date? How much of what you have for /etc/ > > and the like goes back to 2022-Jan-07 or before?) > > > > Alas, that is too true. The system was set up on July 2, 2020 > and I've never managed to make sense of either mergemaster nor > etcupdate. Far as I could tell it didn't matter, the host ran > correctly, until now. > > It's been transplanted to a new hard drive, which allows the > installation of a ports tree. Ports don't install because of > the stale /etc/rc.d/ldconfig file. > > Since no changes have been made to /etc/ apart from /etc/rc.conf > is it possible to simply let mergemaster or etcupdate install > the latest defaults? I have looked at the manpage for etcupdate > and didn't recognize any straightforward way to simply accept > all updates. This particular system is expendable, so I'd be > glad to try things that might not work well, or at all. > > Apologies if I'm being dumb (probably guilty) or lazy (definitely > guilty). The barrage of questions generated by etcupdate and > mergemaster is simply overwhelming. And, I suspect, largely > unnecessary. > > Thanks for reading! > > bob prohaska For a relatively casual way. If I'm facing the same situation, I will... 1. `mergemaster -UFiP` for now, then... 2. `etcupdate extract -B` for next upgrade. And on next upgrade, `etcupdate -p` before installing upgrade, and then `etcupdate -B` after install. You can add -n for dry-run before actual etcupdate. For some notes: mergemaster, the old and less maintained tool, uses current installation and updated tree. Old dedault state is not at all considered. So it could be used for already-updated states. etcupdate, the currently maintained tool, uses previous and updated defaults, and current installation (working environment). It compares differences between old and new default, check if the differences can be sanely applicable to currently working environment or not, and if it's sane, apply the diff automatically. If any conflict happenes, ask the admin (this case, you) for actions. So it requires previous default state, thus cannot use for this case, except you are sure what the actual previous revision was and can prepare the source tree (possibly obj tree, too?) and somehow create "current" tree ATM (will be turned over to "previous" tree on etcupdate run). See manpages for detail. -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221106210716.1c997091ca40ea02ede9f159>