After replying to an e-mail in the bugs@openbsd.org mailing list regarding the borked bootup, Theo de Raadt replied and confirmed that a snapshot went out without the commit for the ABI break, and it was replaced by a newer snapshot that did have it. He recommended updating using a miniroot snapshot.
Downloaded the latest miniroot78 snapshot from an #OpenBSD mirror, brewed some water for my mate as the miniroot78 snapshot image written to a USB drive, and then booted from it on the laptop. Update went through wonderfully and I'm back to a booting OpenBSD system. 🧉
#RunBSD
The runbsd.eu mailserver (OpenBSD + Postfix + Dovecot + OpenDKIM) is just about done. When it is done done, the blogpost will be there too.
The runbsd.eu mailserver (OpenBSD + Postfix + Dovecot + OpenDKIM) is just about done. When it is done done, the blogpost will be there too.
Almost there, just need to check the DANE stuff to get to 100%
The runbsd.eu mailserver (OpenBSD + Postfix + Dovecot + OpenDKIM) is just about done. When it is done done, the blogpost will be there too.
OK How do i recover a borked boot using the miniroot USB ? #OpenBSD
Having answered the question a number of times, I decided to finally document¹ why/how I ended up using BSDs instead of Linux, taking a page from @vermaden's playbook².
tl;dr: a bit of push from Linux, a bit of pull from the BSDs.
RE: https://mastodon.bsd.cafe/@gumnos/115551343732704834
This is a great post.
It's not "against" something - it just explains why Tim prefers to use the BSDs.
Thinking to move this (low-end) laptop away from Linux…
Options:
I can use #NomadBSD to check compatibility hardware with FreeBSD but I am not aware of any "live a la Linux" ISO version for the other two…
Another thing that is confusing me is: I know that FreeBSD uses a partition table similar to Linux, while OpenBSD and NetBSD by default create a lot of partitions; NetBSD also uses letters as MS-DOS for partitions and I am not used anymore to handle partitions this way.
Any recommendation or suggestion is welcomed!
Thanks... 🙏
OK How do i recover a borked boot using the miniroot USB ? #OpenBSD
After replying to an e-mail in the bugs@openbsd.org mailing list regarding the borked bootup, Theo de Raadt replied and confirmed that a snapshot went out without the commit for the ABI break, and it was replaced by a newer snapshot that did have it. He recommended updating using a miniroot snapshot.
Downloaded the latest miniroot78 snapshot from an #OpenBSD mirror, brewed some water for my mate as the miniroot78 snapshot image written to a USB drive, and then booted from it on the laptop. Update went through wonderfully and I'm back to a booting OpenBSD system. 🧉
#RunBSD
Transition to support for 52 partitions https://www.undeadly.org/cgi?action=article;sid=20251114105005 #openbsd #storage #52partitions #disks #bigdisks #partitioning #development #freesoftware #current #libresoftware
Transition to support for 52 partitions https://www.undeadly.org/cgi?action=article;sid=20251114105005 #openbsd #storage #52partitions #disks #bigdisks #partitioning #development #freesoftware #current #libresoftware
Heads up, #OpenBSD -current is preparing for >16 partition disklabels (increased to 52). If you're not using sysupgrade(8), and manually upgrading, you need to pay special attention to this change.
deraadt@ modifed src/sys/*: Begin transition to 52-partition support. The partition encoding used to be lowest 4 bits of dev_t, and now becomes 6. This supplies 64 partitions in struct disklabel.d_partitions[MAXPARTITIONSUNIT], but we only use 52 of these slots (an architecture can be either 16 partition or 52 partition, depending on MD define MAXPARTITIONS). The 52-partition limit is due to single-character representation limit of a-zA-Z. We supply a backwards-compat ioctl for a while which can read an disklabel structure.
This change does not yet store 52-partition information on-disk, and does not transition any architecture to allowing use of >16 partitions.
Those changes come soon, after this compatibility breaking change settles.Immediate result is dev_t numbers for /dev/{sd,wd,rd,fd,...}[12345...][a-p] become incorrect, and need to be repaired. A sysupgrade will do this for automatically. For a hand-build, or a manual kernel replacement, systems which have root NOT ON SD0 or WD0, probably fail into single-user and you must perform these steps explained in /etc/rc:
# fsck /dev/rrootdisk
# mount -uw /dev/rootdisk /
# cd /dev && ./MAKEDEV redodisksPlease do not try to manual-build through this on a system earlier than 7.8.
with and ok krw
This Isn't a Battle
After reading a post describing the FreeBSD community as 'toxic', I share a different perspective. This isn't a battle. It's a reflection on coexistence, the original Open Source spirit, and the quiet richness of taking a different path.
https://my-notes.dragas.net/2025/11/14/this-isnt-a-battle/
#MyNotes #IT #SysAdmin #FreeBSD #NetBSD #OpenBSD #Linux #OpenSource
Tried installing my first non-linux unix the other day. Here are some impressive things about #openbsd :
- Partitions. ~By default, files aren't allowed to be both writable and executable. So `chmod 777` only works in /usr/local~ EDIT: apparently I misunderstood this one.
- The man pages are way more complete than many linux distros. `man afterboot` and `man 8 intro` are great.
- Nice unified service management without the complexity of systemd
- There's a CLI that'll just make RAID volumes for you.
- Nothing more complex than it needs to be. No openssl, only libressl. No sudo, only doas.
- The kernel drivers for recording audio and video by default only record silence and blackness. You need to make a sysctl.conf change if you want to un-blind your laptop. This is both privacy-conscious and hella goth.
7.8 release packages are now ready for #OpenBSD/macppc (powerpc).
https://marc.info/?l=openbsd-cvs&m=176304648812957&w=2
EDIT: They appear to be still being copied out to mirrors, so stay tuned.. the packages in the snapshots directory (date Nov 13) are for 7.8, so you can use -Dsnap in the interim.