<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/lib/libbe/libbe.3, branch release/14.4.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F14.4.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F14.4.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2026-01-20T04:08:09Z</updated>
<entry>
<title>bectl: log modifying functions to zpool history</title>
<updated>2026-01-20T04:08:09Z</updated>
<author>
<name>Rob Norris</name>
<email>rob.norris@klarasystems.com</email>
</author>
<published>2025-12-17T17:00:47Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=919c1e19058d2e214fa3c33498123adb6ca3366c'/>
<id>urn:sha1:919c1e19058d2e214fa3c33498123adb6ca3366c</id>
<content type='text'>
Modeled directly after the method used by the zfs/zpool commands: flag
commands with a "please log me" flag, and when there, reconstruct the
command line. On success, call the library function to add it to the
log.

(Majority of the change by Rob; minor edits by kevans@)

Signed-off-by: Rob Norris &lt;rob.norris@klarasystems.com&gt;
Co-authored-by:	Kyle Evans &lt;kevans@FreeBSD.org&gt;
Sponsored by:	Modirum MDPay
Sponsored by:	Klara, Inc.
(cherry picked from commit 2a87929671e6e6919c18f2c25d60f2c73c3d18f4)
</content>
</entry>
<entry>
<title>libbe: don't hardcode /tmp</title>
<updated>2025-04-26T03:24:13Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2025-04-21T03:47:59Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=8dc42b80fdfb0f39ba52560ac35b6914c72fcff5'/>
<id>urn:sha1:8dc42b80fdfb0f39ba52560ac35b6914c72fcff5</id>
<content type='text'>
Respect $TMPDIR if it's set, fallback to _PATH_TMP (not hardcoded /tmp)
if it's not.

Bump .Dd after recent commits.

Reviewed by:	rcm

(cherry picked from commit 2f11393fee4d60d38634a261edf9aa9fea39c75c)
</content>
</entry>
<entry>
<title>libbe: attempt to remove autocreated mountpoints at unmount time</title>
<updated>2025-04-26T03:23:55Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2025-04-21T03:47:59Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0635fe29225b5a4ecac63fc9d95dff63517d0003'/>
<id>urn:sha1:0635fe29225b5a4ecac63fc9d95dff63517d0003</id>
<content type='text'>
We use a be_mount.XXXX pattern to mkdtemp(3) when creating these, which
seems reasonably unique enough to just continue using that.  Record the
mountpoint of the root dataset and check the dirname of that for the
auto-creation trait.  There's no sense in this bubbling up an error to
callers, so we'll just ignore an error for now.

Requested by:	manu

(cherry picked from commit d6fbae084a2a0e07805633ca46935963357f1efa)
</content>
</entry>
<entry>
<title>libbe: Fix some markup issues.</title>
<updated>2024-03-22T08:07:03Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2024-03-18T13:49:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f25f14a9396ce1378d1ed77e3f137f0c1177d537'/>
<id>urn:sha1:f25f14a9396ce1378d1ed77e3f137f0c1177d537</id>
<content type='text'>
MFC after:	3 days
Reviewed by:	kevans
Differential Revision:	https://reviews.freebsd.org/D44407

(cherry picked from commit ad99fea9045dd3daaeca3d2dd60fffecd2311826)
</content>
</entry>
<entry>
<title>Remove $FreeBSD$: two-line nroff pattern</title>
<updated>2023-08-16T17:55:10Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2023-08-16T17:55:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=fa9896e082a1046ff4fbc75fcba4d18d1f2efc19'/>
<id>urn:sha1:fa9896e082a1046ff4fbc75fcba4d18d1f2efc19</id>
<content type='text'>
Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/
</content>
</entry>
<entry>
<title>spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD</title>
<updated>2023-05-12T16:44:03Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2023-05-10T15:40:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4d846d260e2b9a3d4d0a701462568268cbfe7a5b'/>
<id>urn:sha1:4d846d260e2b9a3d4d0a701462568268cbfe7a5b</id>
<content type='text'>
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.

Discussed with:		pfg
MFC After:		3 days
Sponsored by:		Netflix
</content>
</entry>
<entry>
<title>libbe(3): document be_snapshot()</title>
<updated>2020-10-18T23:42:00Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-10-18T23:42:00Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=513bd2fc81f9a9abad90184dee0af1dafbb55fbe'/>
<id>urn:sha1:513bd2fc81f9a9abad90184dee0af1dafbb55fbe</id>
<content type='text'>
While toying around with lua bindings for libbe(3), I discovered that I
apparently never documented this, despite having documented
be_is_auto_snapshot_name that references it.

MFC after:	1 week
</content>
</entry>
<entry>
<title>libbe(3): const'ify a couple arguments</title>
<updated>2020-10-18T23:32:47Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-10-18T23:32:47Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5773e924e791dfe8cc13049cefbf5f99aab6cc66'/>
<id>urn:sha1:5773e924e791dfe8cc13049cefbf5f99aab6cc66</id>
<content type='text'>
libbe will never need to mutate these as we either process them into a local
buffer or we just don't touch them and write to a separate out argument.

MFC after:	1 week
</content>
</entry>
<entry>
<title>loader: zfs should support bootonce an nextboot</title>
<updated>2020-09-21T09:01:10Z</updated>
<author>
<name>Toomas Soome</name>
<email>tsoome@FreeBSD.org</email>
</author>
<published>2020-09-21T09:01:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e307eb94ae520d98dc1d346a0c53667a41beab5d'/>
<id>urn:sha1:e307eb94ae520d98dc1d346a0c53667a41beab5d</id>
<content type='text'>
bootonce feature is temporary, one time boot, activated by
"bectl activate -t BE", "bectl activate -T BE" will reset the bootonce flag.

By default, the bootonce setting is reset on attempt to boot and the next
boot will use previously active BE.

By setting zfs_bootonce_activate="YES" in rc.conf, the bootonce BE will
be set permanently active.

bootonce dataset name is recorded in boot pool labels, bootenv area.

in case of nextboot, the nextboot_enable boolean variable is recorded in
freebsd:nvstore nvlist, also stored in boot pool label bootenv area.
On boot, the loader will process /boot/nextboot.conf if nextboot_enable
is "YES", and will set nextboot_enable to "NO", preventing /boot/nextboot.conf
processing on next boot.

bootonce and nextboot features are usable in both UEFI and BIOS boot.

To use bootonce/nextboot features, the boot loader needs to be updated on disk;
if loader.efi is stored on ESP, then ESP needs to be updated and
for BIOS boot, stage2 (zfsboot or gptzfsboot) needs to be updated
(gpart or other tools).

At this time, only lua loader is updated.

Sponsored by:	Netflix, Klara Inc.
Differential Revision:	https://reviews.freebsd.org/D25512
</content>
</entry>
<entry>
<title>Drop "All Rights Reserved" from all libbe/bectl files</title>
<updated>2020-01-24T02:18:09Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-01-24T02:18:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6966ac055c3b7a39266fb982493330df7a097997'/>
<id>urn:sha1:6966ac055c3b7a39266fb982493330df7a097997</id>
<content type='text'>
I sent out an e-mail on 2020/01/21 with a plan to do this to Kyle, Rob, and
Wes; all parties have responded in the affirmative that it's OK to drop it
from these files.
</content>
</entry>
</feed>
