It sure would be helpful if "bectl mount" had a -q --quiet option. When using this option, a successful mount would print only the mountpoint used, and nothing else. For example, instead of: $ sudo bectl mount 13.2-RELEASE Successfully mounted 13.2-RELEASE at /tmp/be_mount.PAGF it would instead print $ sudo bectl mount -q 13.2-RELEASE /tmp/be_mount.PAGF With such an option, one could more easily use bectl in scripts, like this: RELEASE=13.2-RELEASE sudo bectl create ${RELEASE} BASEDIR=`sudo bectl mount -q ${RELEASE}`
I wonder if it'd be ok to just change the message..? instead of adding an additional flag. Either way, I agree this. what behavior do you expect when there's a failure?
(In reply to Robert Wing from comment #1) Not sure, because I've never seen a failure from that command before. I guess it would be find to output nothing to stdout, error message to stderr, and exit 1?
(In reply to Alan Somers from comment #2) https://reviews.freebsd.org/D41562
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=760987ecd39b54374aef40783b2c232997f3ac04 commit 760987ecd39b54374aef40783b2c232997f3ac04 Author: Robert Wing <rew@FreeBSD.org> AuthorDate: 2023-08-23 18:39:13 +0000 Commit: Robert Wing <rew@FreeBSD.org> CommitDate: 2023-08-23 18:45:01 +0000 bectl: make mount subcommand less verbose The mount subcommand currently produces output such as: # bectl mount <bootenv> Successfully mounted <bootenv> at <mountpoint> This commit changes it to only print the mountpoint: # bectl mount <bootenv> <mountpoint> This makes it easier to script the mount subcommand. If an error occurs while mounting, an error message is printed to stderr and bectl will exit with a non-zero value. PR: 273180 Reviewed by: kevans, asomers Differential Revision: https://reviews.freebsd.org/D41562 sbin/bectl/bectl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)