svn commit: r336666 - projects/bectl

[Kyle Evans]

I've no idea what the actual intention was- CC'ing Allan Jude since I
was not involved in any way in the original GSoC, I've just
volunteered to try and get it in good enough shape to go into the
tree.

At initial glance of its usage, it seems to be a superset of the beadm
functionality. I do know that it was originally called be(1) in the
GSoC project, and I've renamed it to bectl(8) since:

1.) It's generally agreed that 'be' is too short of a name for
something like this,
2.) It's not strictly compatible with beadm, and
3.) That seems to fit a naming scheme most similar to other similar
utilities in base.

On Tue, Jul 24, 2018 at 11:34 AM, Alan Somers <asomers at freebsd.org> wrote:
> Ahh, that sounds like a good GSoC project.  Is it intended to be fully
> compatible with sysutils/beadm?  If so, then it should probably retain the
> same name.
>
>
> On Tue, Jul 24, 2018 at 10:29 AM, Kyle Evans <kevans at freebsd.org> wrote:
>>
>> bectl is intending to be a C version of sysutils/beadm with the actual
>> functional parts split out into libbe(3).
>>
>> On Tue, Jul 24, 2018 at 11:20 AM, Alan Somers <asomers at freebsd.org> wrote:
>> > So what's the difference between bectl and sysutils/beadm?
>> >
>> >
>> > On Tue, Jul 24, 2018 at 6:55 AM, Kyle Evans <kevans at freebsd.org> wrote:
>> >>
>> >> Author: kevans
>> >> Date: Tue Jul 24 12:55:54 2018
>> >> New Revision: 336666
>> >> URL: https://svnweb.freebsd.org/changeset/base/336666
>> >>
>> >> Log:
>> >>   Create a project branch for bectl(8)
>> >>
>> >>   This will contain an import of libbe/be(1) by Kyle Kneitinger from
>> >> GSoC
>> >> '17,
>> >>   and further work will happen here until it's deemed ready for import
>> >> to
>> >>   head.
>> >>
>> >>   Discussed with:       allanjude
>> >>
>> >> Added:
>> >>      - copied from r336665, head/
>> >> Directory Properties:
>> >>   projects/bectl/   (props changed)
>> >>
>> >
>
>