From nobody Fri Dec 3 13:54:37 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id DD56518CD09B; Fri, 3 Dec 2021 13:54:47 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from transit01.runbox.com (transit01.runbox.com [91.220.196.211]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4J5Dpb5V5vz4kHr; Fri, 3 Dec 2021 13:54:47 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailtransmit02.runbox ([10.9.9.162] helo=aibo.runbox.com) by transit01.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1mt91L-00386M-Pi; Fri, 03 Dec 2021 14:54:39 +0100 Received: from [10.9.9.129] (helo=rmmprod07.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1mt91J-0006nd-UD; Fri, 03 Dec 2021 14:54:38 +0100 Received: from mail by rmmprod07.runbox with local (Exim 4.86_2) (envelope-from ) id 1mt91J-0002Cl-Sx; Fri, 03 Dec 2021 14:54:37 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: from [Authenticated alias (650894)] by runbox.com with http (RMM6); Fri, 03 Dec 2021 13:54:37 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "Miroslav Lachman" <000.fbsd@quip.cz> CC: "Yetoo Happy" , "freebsd-doc" , "freebsd-current" Subject: Re: Make etcupdate bootstrap requirement due to previous mergemaster usage more clear in handbook Date: Fri, 03 Dec 2021 05:54:37 -0800 (PST) X-RMM-Aliasid: 650894 X-Mailer: RMM6 In-Reply-To: <56a60a9b-3d7f-b29e-6074-71078f4b0fe6@quip.cz> Message-Id: X-Rspamd-Queue-Id: 4J5Dpb5V5vz4kHr X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, 3 Dec 2021 13:58:39 +0100, Miroslav Lachman <000.fbsd@quip.cz> wrot= e: > On 03/12/2021 12:52, Yetoo Happy wrote: >=20 > [...] >=20 > > Quick Start* and follow the instructions and get to step > > 7 and may think that even though etcupdate is different from mergemaster > > from the last time they used the handbook they have faith that following > > the instructions won't brick their system. This user will instead find = that > > faith in general is just a very complex facade for the pain and sufferi= ng > > of not following *24.5.6.1 Merging Configuration Files* because the user > > doesn't know that step exists or relevant to the current step and ends = up > > unknowingly having etcupdate append "<<<< yours ... >>>>> new" to the t= op > > of the user's very important configuration files that they didn't expect > > the program to actually modify that way when they resolved differences = nor > > could they predict easily because the diff format is so unintuitive and > > different from mergemaster. Now unable to login or boot into single user > > mode because redirections instead of the actual configuration is parsed= the > > user goes to the handbook to find out what might have happened and scro= lls > > down to find *24.5.6.1 Merging Configuration Files* is under *24.5.6. >=20 > [...] >=20 > That's why I think etcupdate is not so intuitive as tool like this=20 > should be and etcupdate is extremely dangerous because it intentionally=20 > breaks syntax of files vital to have system up and running. > If anything goes wrong with mergemaster automatic process then your have= =20 > configuration not updated which is almost always fine to boot the system= =20 > and fix it. But after etcupdate? Much worse... >=20 > I maintain about 30 machines for 2 decades and had problems with=20 > etcupdate many times. I had ti use mergemaster as fall back many times.=20 > Mainly because of etcupdate said "Reference tree to diff against=20 > unavailable" or "No previous tree to compare against, a sane comparison=20 > is not possible.". And sometimes because etcupdate cannot automatically=20 > update many files in /etc/rc.d and manual merging of a lot of files with= =20 > "<<<< =3D=3D=3D=3D >>>>" is realy painful while with mergemaster only sim= ple=20 > keyboard shortcuts will solve it. > All of this must be very stressful for beginners. >=20 > So beside the update of documentation I really would like to see some=20 > changes to etcupdate workflow where files are modified in temporary=20 > location and moved to destination only if they do not contain any syntax= =20 > breaking changes like <<<<, =3D=3D=3D=3D, >>>>. >=20 > Kind regards > Miroslav Lachman Agree. I fell back to mergemaster this Nov on 13-stable when the /var files pertaining to etcupdate were all missing current /etc data, and no study of man etcupdate was clear enough to rectify such a scenario, and suspect my initial use of etcupdate will or may require a planned reinstall, not havi= ng had to do so since Jan 2004 iirc, [ vs failed hard disk migrations ] and=20 I am just hoping mergemaster stays in /usr/src and updated=20 for system changes, even if moved to 'tools' or something, since its use seems intuitive and much less of a black box.=20 Also, /usr/src/UPDATING still at the bottom emphasizes mergemaster still.= =20=