https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254428
Bug ID: 254428
Summary: bectl(8) manual page update for bectl destroy, without
and with option -o
Product: Documentation
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Manual Pages
Assignee: b...@freebsd.org
Reporter: grahamper...@gmail.com
CC: d...@freebsd.org
<https://cgit.freebsd.org/src/commit/sbin/bectl?id=8338f584dc6e4b8bc6257bcce210d068f8280e3c&h=main>
(2019-10-16):
> bectl(8): destroy: use BE_DESTROY_AUTOORIGIN if -o is not specified
>
> -o will force the origin to be destroyed unconditionally.
>
> BE_DESTROY_AUTOORIGIN, on the other hand, will only destroy the
> origin if it matches the format used by be_snapshot. This lets us
> clean up the snapshots that are clearly not user-managed (because
> we're creating them) while leaving user-created snapshots in place
> and warning that they're still around when the BE created goes away.
From the manual page, for bectl destroy:
> … By default, bectl will warn that it is not destroying the origin of beName.
> …
Is this statement of default behaviour suitably descriptive of the changes that
were introduced in 2019?
Commentary under
<https://vermaden.wordpress.com/2021/02/23/upgrade-freebsd-with-zfs-boot-environments/#comment-18498>
may be indicative of misunderstanding, or partial understanding.
(Do beadm(1) and bectl(8) share the same format for be_snapshot? And so on.)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
