Freebsd 14.1 p4 is out

[NapoleonWils0n]

just a heads up that Freebsd 14.1 p4 is out

a little tip

when you do a pkg update and see freebsd-release-manifests listed
its a good time to check if there is a an update for freebsd

freebsd-update fetch

sudo freebsd-update fetch

create a new boot environment with beadm

sudo beadm create 14.1-p4

activate the new beadm boot environment

sudo beadm activate 14.1-p4

reboot

sudo reboot

freebsd-update install

sudo freebsd-update install

reboot again for good measure

sudo reboot

 

[SirDice]

just a heads up that Freebsd 14.1 p4 is out

Yes.

FreeBSD-EN-24:15.calendar

Continue reading...

forums.freebsd.org

FreeBSD-SA-24:14.umtx

Continue reading...

forums.freebsd.org

FreeBSD-SA-24:13.openssl

Continue reading...

forums.freebsd.org

FreeBSD-SA-24:12.bhyve

Continue reading...

forums.freebsd.org

FreeBSD-SA-24:11.ctl

Continue reading...

forums.freebsd.org

FreeBSD-SA-24:10.bhyve

Continue reading...

forums.freebsd.org

FreeBSD-SA-24:09.libnv

Continue reading...

forums.freebsd.org

 

[NapoleonWils0n]

upgraded 3 machines

2 macs and 1 dell

one thing i did notice is that i now get the apple logo
show up before the geli password prompt on my macs

im pretty sure when booting freebsd on a mac it just used to go straight to the geli prompt
and didnt show the apple logo during boot

just thought id mention it

 

[suntzu00]

beadm is no longer needed as FreeBSD comes with bectl(). by default every time your run freebsd-update install, a new BE is created for you.
.

 

[NapoleonWils0n]

cheers mate

so no need to manually create the BE

 

[suntzu00]

double check to to be sure.

run bectl list and see the output. should be something like this:

13.3-RELEASE-p1_2024-04-26_121046
13.3-RELEASE-p2_2024-06-20_104703
13.3-RELEASE-p3_2024-07-01_112248
13.3-RELEASE-p4_2024-08-09_114348
13.3-RELEASE-p5_2024-09-04_223703

also have a look at /etc/freebsd-update.conf and check the last line( CreateBootEnv -> the default is yes)

 

[NapoleonWils0n]

"Default configuration options" are the default options,
but because its commented out you might think you need to uncomment them to enable them

but i dont think thats the case
unless i have it arse about elbow

/etc/freebsd-update.conf

### Default configuration options:

# Directory in which to store downloaded updates and temporary
# files used by FreeBSD Update.
# WorkDir /var/db/freebsd-update

# Destination to send output of "freebsd-update cron" if an error
# occurs or updates have been downloaded.
# MailTo root

# Is FreeBSD Update allowed to create new files?
# AllowAdd yes

# Is FreeBSD Update allowed to delete files?
# AllowDelete yes

# If the user has modified file ownership, permissions, or flags, should
# FreeBSD Update retain this modified metadata when installing a new version
# of that file?
# KeepModifiedMetadata yes

# When upgrading between releases, should the list of Components be
# read strictly (StrictComponents yes) or merely as a list of components
# which *might* be installed of which FreeBSD Update should figure out
# which actually are installed and upgrade those (StrictComponents no)?
# StrictComponents no

# When installing a new kernel perform a backup of the old one first
# so it is possible to boot the old kernel in case of problems.
# BackupKernel yes

# If BackupKernel is enabled, the backup kernel is saved to this
# directory.
# BackupKernelDir /boot/kernel.old

# When backing up a kernel also back up debug symbol files?
# BackupKernelSymbolFiles no

# Create a new boot environment when installing patches
# CreateBootEnv yes

 

[suntzu00]

so you should have the BEs automatically created before the system update.

what's the output of bectl list?

 

[Cath O'Deray]

no need to manually create the BE

If you chose to override the automation: I do like your approach. You know that 14.1-p4 will be the environment with that version of the OS.

 

[Cath O'Deray]

so you should have the BEs automatically created …

No, as shown, it was commented out in NapoleonWils0n's case.

Sorry, ignore that.

NapoleonWils0n the feature is enabled by default without reliance upon the configuration file.

An override involves commenting out and altering the relevant line.