xref: /freebsd/usr.sbin/etcupdate/etcupdate.8 (revision 3c4ba5f55438f7afd4f4b0b56f88f2bb505fd6a6)
1.\" Copyright (c) 2010-2013 Hudson River Trading LLC
2.\" Written by: John H. Baldwin <jhb@FreeBSD.org>
3.\" All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\"    notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\"
14.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
24.\" SUCH DAMAGE.
25.\"
26.\" $FreeBSD$
27.\"
28.Dd August 9, 2022
29.Dt ETCUPDATE 8
30.Os
31.Sh NAME
32.Nm etcupdate
33.Nd "manage updates to system files not updated by installworld"
34.Sh SYNOPSIS
35.Nm
36.Op Fl npBFN
37.Op Fl d Ar workdir
38.Op Fl r | Fl s Ar source | Fl t Ar tarball
39.Op Fl A Ar patterns
40.Op Fl D Ar destdir
41.Op Fl I Ar patterns
42.Op Fl L Ar logfile
43.Op Fl M Ar options
44.Op Fl m Ar make
45.Nm
46.Cm build
47.Op Fl BN
48.Op Fl d Ar workdir
49.Op Fl s Ar source
50.Op Fl L Ar logfile
51.Op Fl M Ar options
52.Op Fl m Ar make
53.Ar tarball
54.Nm
55.Cm diff
56.Op Fl d Ar workdir
57.Op Fl D Ar destdir
58.Op Fl I Ar patterns
59.Op Fl L Ar logfile
60.Nm
61.Cm extract
62.Op Fl BN
63.Op Fl d Ar workdir
64.Op Fl s Ar source | Fl t Ar tarball
65.Op Fl D Ar destdir
66.Op Fl L Ar logfile
67.Op Fl M Ar options
68.Op Fl m Ar make
69.Nm
70.Cm resolve
71.Op Fl p
72.Op Fl d Ar workdir
73.Op Fl D Ar destdir
74.Op Fl L Ar logfile
75.Nm
76.Cm revert
77.Op Fl d Ar workdir
78.Op Fl D Ar destdir
79.Op Fl L Ar logfile
80.Ar
81.Nm
82.Cm status
83.Op Fl d Ar workdir
84.Op Fl D Ar destdir
85.Sh DESCRIPTION
86The
87.Nm
88utility is a tool for managing updates to files that are not updated as
89part of
90.Sq make installworld
91such as files in
92.Pa /etc .
93It manages updates by doing a three-way merge of changes made to these
94files against the local versions.
95It is also designed to minimize the amount of user intervention with
96the goal of simplifying upgrades for clusters of machines.
97.Pp
98To perform a three-way merge,
99.Nm
100keeps copies of the current and previous versions of files that it manages.
101These copies are stored in two trees known as the
102.Dq current
103and
104.Dq previous
105trees.
106During a merge,
107.Nm
108compares the
109.Dq current
110and
111.Dq previous
112copies of each file to determine which changes need to be merged into the
113local version of each file.
114If a file can be updated without generating a conflict,
115.Nm
116will update the file automatically.
117If the local changes to a file conflict with the changes made to a file in
118the source tree,
119then a merge conflict is generated.
120The conflict must be resolved after the merge has finished.
121The
122.Nm
123utility will not perform a new merge until all conflicts from an earlier
124merge are resolved.
125.Sh MODES
126The
127.Nm
128utility supports several modes of operation.
129The mode is specified via an optional command argument.
130If present, the command must be the first argument on the command line.
131If a command is not specified, the default mode is used.
132.Ss Default Mode
133The default mode merges changes from the source tree to the destination
134directory.
135First,
136it updates the
137.Dq current
138and
139.Dq previous
140trees.
141Next,
142it compares the two trees merging changes into the destination directory.
143Finally,
144it displays warnings for any conditions it could not handle automatically.
145.Pp
146If the
147.Fl r
148option is not specified,
149then the first step taken is to update the
150.Dq current
151and
152.Dq previous
153trees.
154If a
155.Dq current
156tree already exists,
157then that tree is saved as the
158.Dq previous
159tree.
160An older
161.Dq previous
162tree is removed if it exists.
163By default the new
164.Dq current
165tree is built from a source tree.
166However,
167if a tarball is specified via the
168.Fl t
169option,
170then the tree is extracted from that tarball instead.
171.Pp
172Next,
173.Nm
174compares the files in the
175.Dq current
176and
177.Dq previous
178trees.
179If a file was removed from the
180.Dq current
181tree,
182then it will be removed from the destination directory only if it
183does not have any local modifications.
184If a file was added to the
185.Dq current
186tree,
187then it will be copied to the destination directory only if it
188would not clobber an existing file.
189If a file is changed in the
190.Dq current
191tree,
192then
193.Nm
194will attempt to merge the changes into the version of the file in the
195destination directory.
196If the merge encounters conflicts,
197then a version of the file with conflict markers will be saved for
198future resolution.
199If the merge does not encounter conflicts,
200then the merged version of the file will be saved in the destination
201directory.
202If
203.Nm
204is not able to safely merge in changes to a file other than a merge conflict,
205it will generate a warning.
206.Pp
207For each file that is updated a line will be output with a leading character
208to indicate the action taken.
209The possible actions follow:
210.Pp
211.Bl -tag -width "A" -compact -offset indent
212.It A
213Added
214.It C
215Conflict
216.It D
217Deleted
218.It M
219Merged
220.It U
221Updated
222.El
223.Pp
224Finally,
225if any warnings were encountered they are displayed after the merge has
226completed.
227.Pp
228Note that for certain files
229.Nm
230will perform post-install actions any time that the file is updated.
231Specifically,
232.Xr pwd_mkdb 8
233is invoked if
234.Pa /etc/master.passwd
235is changed,
236.Xr cap_mkdb 1
237is invoked to update
238.Pa /etc/login.conf.db
239if
240.Pa /etc/login.conf
241is changed,
242.Xr newaliases 1
243is invoked if
244.Pa /etc/mail/aliases
245is changed,
246.Xr services_mkdb 8
247is invoked if
248.Pa /etc/services
249is changed,
250.Xr tzsetup 8
251is invoked if
252.Pa /etc/localtime
253is changed and if
254.Fa /var/db/zoneinfo
255exists,
256and
257.Pa /etc/rc.d/motd
258is invoked if
259.Pa /etc/motd
260is changed.
261One exception is that if
262.Pa /etc/mail/aliases
263is changed and the destination directory is not the default,
264then a warning will be issued instead.
265This is due to a limitation of the
266.Xr newaliases 1
267command.
268Similarly,
269if
270.Pa /etc/motd
271is changed and the destination directory is not the default,
272then
273.Pa /etc/rc.d/motd
274will not be executed due to a limitation of that script.
275In this case no warning is issued as the result of
276.Pa /etc/rc.d/motd
277is merely cosmetic and will be corrected on the next reboot.
278.Ss Build Mode
279The
280.Cm build
281mode is used to build a tarball that contains a snapshot of a
282.Dq current
283tree.
284This tarball can be used by the default and extract modes.
285Using a tarball can allow
286.Nm
287to perform a merge without requiring a source tree that matches the
288currently installed world.
289The
290.Fa tarball
291argument specifies the name of the file to create.
292The file will be a
293.Xr tar 5
294file compressed with
295.Xr bzip2 1 .
296.Ss Diff Mode
297The
298.Cm diff
299mode compares the versions of files in the destination directory to the
300.Dq current
301tree and generates a unified format diff of the changes.
302This can be used to determine which files have been locally modified and how.
303Note that
304.Nm
305does not manage files that are not maintained in the source tree such as
306.Pa /etc/fstab
307and
308.Pa /etc/rc.conf .
309.Ss Extract Mode
310The
311.Cm extract
312mode generates a new
313.Dq current
314tree.
315Unlike the default mode,
316it does not save any existing
317.Dq current
318tree and does not modify any existing
319.Dq previous
320tree.
321The new
322.Dq current
323tree can either be built from a source tree or extracted from a tarball.
324.Ss Resolve Mode
325The
326.Cm resolve
327mode is used to resolve any conflicts encountered during a merge.
328In this mode,
329.Nm
330iterates over any existing conflicts prompting the user for actions to take
331on each conflicted file.
332For each file, the following actions are available:
333.Pp
334.Bl -tag -width "(tf) theirs-full" -compact
335.It (p)  postpone
336Ignore this conflict for now.
337.It (df) diff-full
338Show all changes made to the merged file as a unified diff.
339.It (e)  edit
340Change the merged file in an editor.
341.It (r)  resolved
342Install the merged version of the file into the destination directory.
343.It (mf) mine-full
344Use the version of the file in the destination directory and ignore any
345changes made to the file in the
346.Dq current
347tree.
348.It (tf) theirs-full
349Use the version of the file from the
350.Dq current
351tree and discard any local changes made to the file.
352.It (h)  help
353Display the list of commands.
354.El
355.Ss Revert Mode
356The
357.Cm revert
358mode is used to restore the stock versions of files.
359In this mode,
360.Nm
361installs the stock version of requested files.
362This mode cannot be used to restore directories, only individual files.
363.Ss Status Mode
364The
365.Cm status
366mode shows a summary of the results of the most recent merge.
367First it lists any files for which there are unresolved conflicts.
368Next it lists any warnings generated during the last merge.
369If the last merge did not generate any conflicts or warnings,
370then nothing will be output.
371.Sh OPTIONS
372The following options are available.
373Note that most options do not apply to all modes.
374.Bl -tag -width ".Fl A Ar patterns"
375.It Fl A Ar patterns
376Always install the new version of any files that match any of the patterns
377listed in
378.Ar patterns .
379Each pattern is evaluated as an
380.Xr sh 1
381shell pattern.
382This option may be specified multiple times to specify multiple patterns.
383Multiple space-separated patterns may also be specified in a single
384option.
385Note that ignored files specified via the
386.Ev IGNORE_FILES
387variable or the
388.Fl I
389option will not be installed.
390.It Fl B
391Do not build generated files in a private object tree.
392Instead,
393reuse the generated files from a previously built object tree that matches
394the source tree.
395This can be useful to avoid gratuitous conflicts in
396.Xr sendmail 8
397configuration
398files when bootstrapping.
399It can also be useful for building a tarball that matches a specific
400world build.
401.It Fl D Ar destdir
402Specify an alternate destination directory as the target of a merge.
403This is analogous to the
404.Dv DESTDIR
405variable used with
406.Sq make installworld .
407The default destination directory is an empty string which results in
408merges updating
409.Pa /etc
410on the local machine.
411.It Fl d Ar workdir
412Specify an alternate directory to use as the work directory.
413The work directory is used to store the
414.Dq current
415and
416.Dq previous
417trees as well as unresolved conflicts.
418The default work directory is
419.Pa <destdir>/var/db/etcupdate .
420.It Fl F
421Ignore changes in the FreeBSD ID string when comparing files in the
422destination directory to files in either of the
423.Dq current
424or
425.Dq previous
426trees.
427In
428.Cm diff
429mode,
430this reduces noise due to FreeBSD ID string changes in the output.
431During an update this can simplify handling for harmless conflicts caused
432by FreeBSD ID string changes.
433.Pp
434Specifically,
435if a file in the destination directory is identical to the same file in the
436.Dq previous
437tree modulo the FreeBSD ID string,
438then the file is treated as if it was unmodified and the
439.Dq current
440version of the file will be installed.
441Similarly,
442if a file in the destination directory is identical to the same file in the
443.Dq current
444tree modulo the FreeBSD ID string,
445then the
446.Dq current
447version of the file will be installed to update the ID string.
448If the
449.Dq previous
450and
451.Dq current
452versions of the file are identical,
453then
454.Nm
455will not change the file in the destination directory.
456.Pp
457Due to limitations in the
458.Xr diff 1
459command,
460this option may not have an effect if there are other changes in a file that
461are close to the FreeBSD ID string.
462.It Fl I Ar patterns
463Ignore any files that match any of the patterns listed in
464.Ar patterns .
465No warnings or other messages will be generated for those files during a
466merge.
467Each pattern is evaluated as an
468.Xr sh 1
469shell pattern.
470This option may be specified multiple times to specify multiple patterns.
471Multiple space-separated patterns may also be specified in a single
472option.
473.It Fl L Ar logfile
474Specify an alternate path for the log file.
475The
476.Nm
477utility logs each command that it invokes along with the standard output
478and standard error to this file.
479By default the log file is stored in a file named
480.Pa log
481in the work directory.
482.It Fl M Ar options
483Pass
484.Ar options
485as additional parameters to
486.Xr make 1
487when building a
488.Dq current
489tree.
490This can be used for to set the
491.Dv TARGET
492or
493.Dv TARGET_ARCH
494variables for a cross-build.
495.It Fl m Ar make
496Use
497.Ar make
498as the
499.Xr make 1
500binary when building a
501.Dq current
502tree.
503.It Fl n
504Enable
505.Dq dry-run
506mode.
507Do not merge any changes to the destination directory.
508Instead,
509report what actions would be taken during a merge.
510Note that the existing
511.Dq current
512and
513.Dq previous
514trees will not be changed.
515If the
516.Fl r
517option is not specified,
518then a temporary
519.Dq current
520tree will be extracted to perform the comparison.
521.It Fl N
522Perform a
523.Dv NO_ROOT
524build when building a
525.Dq current
526tree.
527The resulting tree will include a corresponding
528.Pa METALOG
529file at its root.
530.It Fl p
531Enable
532.Dq pre-world
533mode.
534Only merge changes to files that are necessary to successfully run
535.Sq make installworld
536or
537.Sq make installkernel .
538When this flag is enabled,
539the existing
540.Dq current
541and
542.Dq previous
543trees are left alone.
544Instead,
545a temporary tree is populated with the necessary files.
546This temporary tree is compared against the
547.Dq current
548tree.
549This allows a normal update to be run after
550.Sq make installworld
551has completed.
552Any conflicts generated during a
553.Dq pre-world
554update should be resolved by a
555.Dq pre-world
556.Cm resolve .
557.It Fl r
558Do not update the
559.Dq current
560and
561.Dq previous
562trees during a merge.
563This can be used to
564.Dq re-run
565a previous merge operation.
566.It Fl s Ar source
567Specify an alternate source tree to use when building or extracting a
568.Dq current
569tree.
570The default source tree is
571.Pa /usr/src .
572.It Fl t Ar tarball
573Extract a new
574.Dq current
575tree from a tarball previously generated by the
576.Cm build
577command rather than building the tree from a source tree.
578.El
579.Sh CONFIG FILE
580The
581.Nm
582utility can also be configured by setting variables in an optional
583configuration file named
584.Pa /etc/etcupdate.conf .
585Note that command line options override settings in the configuration file.
586The configuration file is executed by
587.Xr sh 1 ,
588so it uses that syntax to set configuration variables.
589The following variables can be set:
590.Bl -tag -width ".Ev ALWAYS_INSTALL"
591.It Ev ALWAYS_INSTALL
592Always install files that match any of the patterns listed in this variable
593similar to the
594.Fl A
595option.
596.It Ev DESTDIR
597Specify an alternate destination directory similar to the
598.Fl D
599option.
600.It Ev EDITOR
601Specify a program to edit merge conflicts.
602.It Ev FREEBSD_ID
603Ignore changes in the FreeBSD ID string similar to the
604.Fl F
605option.
606This is enabled by setting the variable to a non-empty value.
607.It Ev IGNORE_FILES
608Ignore files that match any of the patterns listed in this variable
609similar to the
610.Fl I
611option.
612.It Ev LOGFILE
613Specify an alternate path for the log file similar to the
614.Fl L
615option.
616.It Ev MAKE_CMD
617Specify the
618.Xr make 1
619binary when building a
620.Dq current
621tree similar to the
622.Fl m
623option.
624.It Ev MAKE_OPTIONS
625Pass additional options to
626.Xr make 1
627when building a
628.Dq current
629tree similar to the
630.Fl M
631option.
632.It Ev SRCDIR
633Specify an alternate source tree similar to the
634.Fl s
635option.
636.It Ev WORKDIR
637Specify an alternate work directory similar to the
638.Fl d
639option.
640.El
641.Sh ENVIRONMENT
642The
643.Nm
644utility uses the program identified in the
645.Ev EDITOR
646environment variable to edit merge conflicts.
647If
648.Ev EDITOR
649is not set,
650.Xr vi 1
651is used as the default editor.
652.Sh FILES
653.Bl -tag -width ".Pa /var/db/etcupdate/log" -compact
654.It Pa /etc/etcupdate.conf
655Optional config file.
656.It Pa /var/db/etcupdate
657Default work directory used to store trees and other data.
658.It Pa /var/db/etcupdate/log
659Default log file.
660.El
661.Sh EXIT STATUS
662.Ex -std
663.Sh EXAMPLES
664To compare the files in
665.Pa /etc
666with the stock versions:
667.Pp
668.Dl "etcupdate diff"
669.Pp
670To merge changes after an upgrade via the buildworld and installworld process:
671.Pp
672.Dl "etcupdate"
673.Pp
674To resolve any conflicts generated during a merge:
675.Pp
676.Dl "etcupdate resolve"
677.Ss Bootstrapping
678The
679.Nm
680utility may need to be bootstrapped before it can be used.
681The
682.Cm diff
683command will fail with an error about a missing reference tree if
684bootstrapping is needed.
685.Pp
686Bootstrapping
687.Nm
688requires a source tree that matches the currently installed world.
689The easiest way to ensure this is to bootstrap
690.Nm
691before updating the source tree to start the next world upgrade cycle.
692First,
693generate a reference tree:
694.Pp
695.Dl "etcupdate extract"
696.Pp
697Second,
698use the
699.Cm diff
700command to compare the reference tree to your current files in
701.Pa /etc .
702Undesired differences should be removed using an editor,
703.Xr patch 1 ,
704or by copying files from the reference tree
705.Po
706located at
707.Pa /var/db/etcupdate/current
708by default
709.Pc
710.
711.Pp
712If the tree at
713.Pa /usr/src
714is already newer than the currently installed world,
715a new tree matching the currently installed world can be checked out to
716a temporary location.
717The reference tree for
718.Nm
719can then be generated via:
720.Pp
721.Dl "etcupdate extract -s /path/to/tree"
722.Pp
723The
724.Cm diff
725command can be used as above to remove undesired differences.
726Afterwards,
727the changes in the tree at
728.Pa /usr/src
729can be merged via a regular merge.
730.Sh DIAGNOSTICS
731The following warning messages may be generated during a merge.
732Note that several of these warnings cover obscure cases that should occur
733rarely if at all in practice.
734For example,
735if a file changes from a file to a directory in the
736.Dq current
737tree
738and the file was modified in the destination directory,
739then a warning will be triggered.
740In general,
741when a warning references a pathname,
742the corresponding file in the destination directory is not changed by a
743merge operation.
744.Bl -diag
745.It "Directory mismatch: <path> (<type>)"
746An attempt was made to create a directory at
747.Pa path
748but an existing file of type
749.Dq type
750already exists for that path name.
751.It "Modified link changed: <file> (<old> became <new>)"
752The target of a symbolic link named
753.Pa file
754was changed from
755.Dq old
756to
757.Dq new
758in the
759.Dq current
760tree.
761The symbolic link has been modified to point to a target that is neither
762.Dq old
763nor
764.Dq new
765in the destination directory.
766.It "Modified mismatch: <file> (<new> vs <dest>)"
767A file named
768.Pa file
769of type
770.Dq new
771was modified in the
772.Dq current
773tree,
774but the file exists as a different type
775.Dq dest
776in the destination directory.
777.It "Modified <type> changed: <file> (<old> became <new>)"
778A file named
779.Pa file
780changed type from
781.Dq old
782in the
783.Dq previous
784tree to type
785.Dq new
786in the
787.Dq current
788tree.
789The file in the destination directory of type
790.Dq type
791has been modified,
792so it could not be merged automatically.
793.It "Modified <type> remains: <file>"
794The file of type
795.Dq type
796named
797.Pa file
798has been removed from the
799.Dq current
800tree,
801but it has been locally modified.
802The modified version of the file remains in the destination directory.
803.It "Needs update: /etc/localtime (required manual update via tzsetup(8))"
804The
805.Fa /var/db/zoneinfo
806file does not exist,
807so
808.Nm
809was not able to refresh
810.Fa /etc/localtime
811from its source file in
812.Fa /usr/share/zoneinfo .
813Running
814.Xr tzsetup 8
815will both refresh
816.Fa /etc/localtime
817and generate
818.Fa /var/db/zoneinfo
819permitting future updates to refresh
820.Fa /etc/localtime
821automatically.
822.It "Needs update: /etc/mail/aliases.db (required manual update via newaliases(1))"
823The file
824.Pa /etc/mail/aliases
825was updated during a merge with a non-empty destination directory.
826Due to a limitation of the
827.Xr newaliases 1
828command,
829.Nm
830was not able to automatically update the corresponding aliases database.
831.It "New file mismatch: <file> (<new> vs <dest>)"
832A new file named
833.Pa file
834of type
835.Dq new
836has been added to the
837.Dq current
838tree.
839A file of that name already exists in the destination directory,
840but it is of a different type
841.Dq dest .
842.It "New link conflict: <file> (<new> vs <dest>)"
843A symbolic link named
844.Pa file
845has been added to the
846.Dq current
847tree that links to
848.Dq new .
849A symbolic link of the same name already exists in the destination
850directory,
851but it links to a different target
852.Dq dest .
853.It "Non-empty directory remains: <file>"
854The directory
855.Pa file
856was removed from the
857.Dq current
858tree,
859but it contains additional files in the destination directory.
860These additional files as well as the directory remain.
861.It "Remove mismatch: <file> (<old> became <new>)"
862A file named
863.Pa file
864changed from type
865.Dq old
866in the
867.Dq previous
868tree to type
869.Dq new
870in the
871.Dq current
872tree,
873but it has been removed in the destination directory.
874.It "Removed file changed: <file>"
875A file named
876.Pa file
877was modified in the
878.Dq current
879tree,
880but it has been removed in the destination directory.
881.It "Removed link changed: <file> (<old> became <new>)"
882The target of a symbolic link named
883.Pa file
884was changed from
885.Dq old
886to
887.Dq new
888in the
889.Dq current
890tree,
891but it has been removed in the destination directory.
892.El
893.Sh SEE ALSO
894.Xr cap_mkdb 1 ,
895.Xr diff 1 ,
896.Xr make 1 ,
897.Xr newaliases 1 ,
898.Xr sh 1 ,
899.Xr mergemaster 8 ,
900.Xr pwd_mkdb 8 ,
901.Xr services_mkdb 8 ,
902.Xr tzsetup 8
903.Sh HISTORY
904The
905.Nm
906utility first appeared in
907.Fx 10.0 .
908.Sh AUTHORS
909The
910.Nm
911utility was written by
912.An John Baldwin Aq Mt jhb@FreeBSD.org .
913.Sh BUGS
914Rerunning a merge does not automatically delete conflicts left over from a
915previous merge.
916Any conflicts must be resolved before the merge can be rerun.
917It is not clear if this is a feature or a bug.
918.Pp
919There is no way to easily automate conflict resolution for specific files.
920For example, one can imagine a syntax along the lines of
921.Pp
922.Dl "etcupdate resolve tf /some/file"
923.Pp
924to resolve a specific conflict in an automated fashion.
925.Pp
926Bootstrapping
927.Nm
928often results in gratuitous diffs in
929.Pa /etc/mail/*.cf
930that cause conflicts in the first merge.
931If an object tree that matches the source tree is present when bootstrapping,
932then passing the
933.Fl B
934flag to the
935.Cm extract
936command can work around this.
937