FreeBSD 13.1

When will the new iso based on 13.1 be released?

1 Like

Which iso? The one for FreeBSD (which may or may not be an .iso file depending on the architecture you are running it) or the one for NomadBSD (which is definitely not an .iso but an .img file)?

Just do an upgrade. I did it yesterday without issues.

# freebsd-update -r FreeBSD 13.1-RELEASE upgrade

# shutdown -r now

# freebsd-update install

Follow the instructions provided with the upgrade. If you have custom configurations, such as in /etc/groups, it will have you merge those files manually during the upgrade. Just follow the instructions provided during the upgrade.

1 Like

For more details on upgrading to FreeBSD 13.1 look in this thread.

1 Like

@tthenrie Did you do this on a “installed” version or on the live USB directly?

I ran out of diskspace on the live media. :frowning:
(Stock IMG no applications installed)

I have my system installed on the laptop’s SSD. I seem to recall, though, that I ran into a similar problem when I tried to upgrade on my USB. As I recall, it stems from certain directories on the USB install being restricted in size, rather than actual disk space. I cannot recall right now how I resolved the issue, but I believe there was a thread on this forum that helped me. I’ll see if I can find it and provide a link.

Hello @phix,
welcome to the forum.

I’ve had the same problem and meant to post my solution here, but forgot about it.
I will write a post tonight…

Hi!

Thanks for your replies.

I ended up building Nomad from “source” and rebase it on 13.1.
However, the master branch did not build out of the box so I had to do a few modifications to the pkg list.
But hopefully it should be all right. :slight_smile: (I’m all new to BSD)

Lets hope we get an official 13.1 image soon. I think Nomad is an amazing OS. <3

3 Likes

The NomadBSD-image can be tricky to upgrade to FreeBSD 13.1 because the layout on the disk is lean and optimized for maximum user-space.
So I experienced problems upgrading a vanilla NomadBSD 130R-20210508 on a 16 GB USB-stick. It ran out of disk-space on /ROOT/ and choked.

During upgrade the old 13.0 kernel is kept and renamed to /boot/kernel.old. But you can change this behaviour (and instead delete the old kernel during upgrade) in freebsd-update.conf - and that gives the system juuust enough disk-space to complete the upgrade.

So before running freebsd-update, you have to open the freebsd-update.conf (with root privileges)

> sudo vim /etc/freebsd-update.conf

and (near the bottom) uncomment and change the line # BackupKernel yes to:

BackupKernel no

or simply use this command:

sudo sed -i.old 's/# BackupKernel yes/BackupKernel no/' /etc/freebsd-update.conf

Happy upgrading :slight_smile:

Please chime in with corrections and addition :slight_smile:

1 Like

Not possible with the range of computers that FreeBSD 13.0-RELEASE can not boot, a considerably broad range:

Hello,

I was looking for a long time persistent live system and Nomad is very beautiful and practice.
Thanks to Nomad Teams for making this nice FreeBSD distro
I use it since a long time

I reinstalled NomadBSD to use lastest FreeBSD 13.1 on SSD disk 240GB because some of the upgraded packages are build for the kernel 1301000 and FreeBSD 13.0 has the kernel 1300139.
and FreeBSD 13.0 end-of-life
https://lists.freebsd.org/archives/freebsd-announce/2022-August/000044.html

I installed NomadBSD 130R-20210508 and before freebsd-update I do
sudo sed -i.old ‘s/# BackupKernel yes/BackupKernel no/’ /etc/freebsd-update.conf
reboot…freebsd-update upgrade -r 13.1-RELEASE…

During upgrade I have disk-space on /ROOT/ but I continued

Actually NomadBSD is running and I can update packages but /dev/label/nomadroot and filesystem full are full

I can reinstall it to use lastest FreeBSD 13.1, do you have solution:

Thanks a lot

nomad@NomadBSD$ uname -a
FreeBSD NomadBSD 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 GENERIC amd64

nomad@NomadBSD$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/label/nomadroot 3,4G 3,1G -16M 101% /
devfs 1,0K 1,0K 0B 100% /dev
tmpfs 10G 248M 9,7G 2% /tmp
tmpfs 9,7G 156K 9,7G 0% /var/log
procfs 4,0K 4,0K 0B 100% /proc
/dev/label/nomaddata.eli 231G 89G 124G 42% /data
/dev/md0.uzip 6,6G 6,0G 651M 90% /unionfs/usr/local
/dev/fuse 238G 96G 124G 44% /usr/local
/data/compat 231G 89G 124G 42% /compat
/data/var/tmp 231G 89G 124G 42% /var/tmp
/data/var/db 231G 89G 124G 42% /var/db
/data/usr/ports 231G 89G 124G 42% /usr/ports

nomad@NomadBSD$ dmesg | grep ‘filesystem full’
pid 2005 (avahi-daemon), uid 558 inumber 294147 on /: filesystem full
pid 2630 (pactl), uid 1001 inumber 294156 on /: filesystem full
pid 2614 (plank), uid 1001 inumber 357648 on /: filesystem full
pid 2614 (plank), uid 1001 inumber 357748 on /: filesystem full
pid 2614 (plank), uid 1001 inumber 357748 on /: filesystem full
pid 2614 (plank), uid 1001 inumber 293685 on /: filesystem full
pid 3633 (xfce4-screenshooter), uid 1001 inumber 358130 on /: filesystem full
pid 3633 (xfce4-screenshooter), uid 1001 inumber 358185 on /: filesystem full
pid 3633 (xfce4-screenshooter), uid 1001 inumber 357762 on /: filesystem full
pid 3633 (xfce4-screenshooter), uid 1001 inumber 357762 on /: filesystem full
pid 2614 (plank), uid 1001 inumber 357762 on /: filesystem full
pid 3652 (thunderbird), uid 1001 inumber 358130 on /: filesystem full
pid 3652 (thunderbird), uid 1001 inumber 357762 on /: filesystem full
pid 3652 (thunderbird), uid 1001 inumber 357762 on /: filesystem full
pid 3652 (thunderbird), uid 1001 inumber 357762 on /: filesystem full
pid 3652 (thunderbird), uid 1001 inumber 358130 on /: filesystem full
pid 3652 (thunderbird), uid 1001 inumber 358130 on /: filesystem full
pid 3652 (thunderbird), uid 1001 inumber 357762 on /: filesystem full