Date: Tue, 19 Mar 2019 19:13:39 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 235850] bectl(8): create should mention it creates from booted system without any other argument Message-ID: <bug-235850-9-QpplbLosrW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235850-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235850 Kyle Evans <kevans@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kevans@freebsd.org --- Comment #3 from Kyle Evans <kevans@freebsd.org> --- (In reply to Mateusz Piotrowski from comment #1) Right, he's talking specifically about the 'create' subcommand. I note that the man page here is kind of... bad. We should do the following: 1.) Get rid of the bectl create [-r] beName@snapshot line in SYNOPSIS 2.) Get rid of the same down in commands 3.) Amend the create command description to mention: If the .Fl e argument is specified, the new environment will be cloned from the given nonActiveBE | beName@snapshot. When the .Fl e argument is not specified, the new environment will be created from the currently booted environment. If .Nm is creating from another boot environment, a snapshot of that boot environment will be created to clone from. Of course, the markup is basically all wrong, but I think that gets the idea across. We should mention for those not familiar with bectl that the default is to use the currently booted environment, and we should mention for those maybe not necessarily familiar with some of the underlying ZFS terminology that create of anything other than beName@snapshot implies that a snapshot of that boot environment will be made for creation. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235850-9-QpplbLosrW>