freebsd

<https://redd.it/1rgx8ts> … thirty-six hours later, no-one has spotted the two deliberate mistakes.

Note to self: be genuinely careless more often. Much more. Especially at weekends, when no-one's paying attention 🙃

#FreeBSD #weekend #stikethough

Community... help!

Can someone explain me how to add my laptops to the #FreeBSD Laptop Integration Testing Project? My knowledge of git is limited. I clone, I make but where do I send the pull request? My fork? Only there I am allowed to push changes.

Thanks for the help in advance!

Anyone have any go-to choice for #FreeBSD scripts to handle zfs-send of snapshots for backup purposes? I have a couple of hosts using zfs and already have snapshots set up, but I would like to have the most recent snapshot sent to another host (and older snapshots to be pruned from that remote host).

Doesn't need to be anything super-fancy beyond that, bonus points for just integrating with periodic(8)

Thanks to the #FreeBSD Handbook on Ports and the following page, I finally got around to building the drm-kmod port and dependencies so that amdgpu runs properly on 14.2.

https://forums.freebsd.org/threads/freebsd-14-2-graphics-fix.96365/

#RunBSD #BSD

$ id

Get your user ID & group info on a *BSD Linux system

🖋️ #bash #sh #zsh #ksh #csh #tsh #programming #freeBSD #POSIX #Linux

AISLE Discovers CVE-2026-42511: a 21-Year-Old #FreeBSD Remote Command Execution Vulnerability

https://aisle.com/blog/aisle-discovers-cve-2026-42511-a-21-year-old-freebsd-remote-command-execution-vulnerability

Call for testing KDE installer dialogs

<https://gitlab.com/alfix/kde-installer-dialogs/-/blob/main/cft.md> | <https://github.com/alfonsosiciliano/kde-installer-dialogs/blob/main/cft.md> @alfonsosiciliano

<https://lists.freebsd.org/archives/freebsd-desktop/2026-January/007438.html> | <https://www.reddit.com/r/freebsd/comments/1qihyal/call_for_testing_kde_installer_dialogs_alfonso/>

Cc @kde @kdedude @FreeBSDFoundation

#CFT #KDE #Plasma #desktop #FreeBSD #installer #install #bsdinstall

Review: Sylve on FreeBSD https://lobste.rs/s/dvsuag #freebsd #security
https://distrowatch.com/weekly-mobile.php?issue=20260518#sylve

Well I can confirm that on my #FreeBSD #ThinkPad using the AX200 WiFi setup with lagg works solidly after a wee doas service netif restart && doas service routing restart. On first boot sometimes it gets WiFi and then drops it and others it just doesn't get. But running the above commands after bootup fixes it and it stays connected.

OK #FreeBSD folk why does #Qutebrowser have to be removed ??? I need it ! Just tried to do an update on FreeBSD 15.0-RELEASE-p2

Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
All repositories are up to date.
Checking for upgrades (22 candidates): 100%
Processing candidates (22 candidates): 100%
The following 27 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
AppStream: 1.1.1 -> 1.1.2 [FreeBSD-ports]
harfbuzz: 12.3.0 -> 12.3.2 [FreeBSD-ports]
harfbuzz-icu: 12.3.0 -> 12.3.2 [FreeBSD-ports]
lcms2: 2.17 -> 2.18 [FreeBSD-ports]
libfyaml: 0.9_1 -> 0.9.3 [FreeBSD-ports]
libgcrypt: 1.11.2 -> 1.12.0 [FreeBSD-ports]
mysql80-client: 8.0.44 -> 8.0.45 [FreeBSD-ports]
orc: 0.4.41_1 -> 0.4.42 [FreeBSD-ports]
pciids: 20251227 -> 20260115 [FreeBSD-ports]
png: 1.6.53 -> 1.6.54 [FreeBSD-ports]
py311-adblock: 0.6.0_48 -> 0.6.0_49 [FreeBSD-ports]
py311-certifi: 2025.11.12 -> 2026.1.4 [FreeBSD-ports]
py311-urllib3: 2.6.2,1 -> 2.6.3,1 [FreeBSD-ports]
spdlog: 1.16.0_1 -> 1.17.0 [FreeBSD-ports]
waybar: 0.14.0_2 -> 0.14.0_3 [FreeBSD-ports]

Installed packages to be REINSTALLED:
ImageMagick7-7.1.2.11 [FreeBSD-ports] (required shared library changed)
cups-filters-1.28.17_12 [FreeBSD-ports] (required shared library changed)
libcdr01-0.1.8_1 [FreeBSD-ports] (required shared library changed)
libfreehand-0.1.2_27 [FreeBSD-ports] (required shared library changed)
libraw-0.21.5 [FreeBSD-ports] (required shared library changed)
libreoffice-25.8.4.2 [FreeBSD-ports] (required shared library changed)
openjdk17-17.0.17+10.1_1 [FreeBSD-ports] (required shared library changed)

Installed packages to be REMOVED:
py311-qt6-webengine: 6.10.0
qt6: 6.10.1
qt6-webengine: 6.10.1_3
qt6-webview: 6.10.1
qutebrowser: 3.6.3

Number of packages to be removed: 5
Number of packages to be upgraded: 15
Number of packages to be reinstalled: 7

The operation will free 291 MiB.
327 MiB to be downloaded.

Proceed with this action? [y/N]:

RESOLVED - See last toot in thread

I've got a weird issue on my #FreeBSD ThinkPad. Since setting up lagg yesterday which worked fine. I powered off last night and then switched it on this morning. I noticed that I had no network access on either the re1 interface or wlan0. I powered off and on and it worked. I have since discovered that if it doesn't work if I just doas service netif restart it starts to work again.

This is my lagg setup in /etc/rc.conf

# WiFi
wlans_iwlwifi0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"
cloned_interfaces="lagg0"
ifconfig_lagg0="up laggproto failover laggport re1 laggport wlan0 DHCP"

This is the output of ifconfig when it's working:

re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
ether 8c:8c:aa:bd:bb:f0
media: Ethernet autoselect (none)
status: no carrier
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
re1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=80088<VLAN_MTU,VLAN_HWCSUM,LINKSTATE>
ether 8c:8c:aa:bd:bb:ef
inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
wlan0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=0
ether 8c:8c:aa:bd:bb:ef
hwaddr 70:9c:d1:af:ad:93
inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255
groups: wlan
ssid Smithies channel 40 (5200 MHz 11a vht/80-) bssid f0:9f:c2:ab:8d:c3
regdomain FCC country US authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit AES-CCM ucast:128-bit txpower 17
bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k
ampdudensity 8 -amsdutx amsdurx shortgi -ldpctx ldpcrx -uapsd vht
vht40 vht80 vht160 -vht80p80 wme roaming MANUAL
parent interface: iwlwifi0
media: IEEE 802.11 Wireless Ethernet VHT mode 11ac
status: associated
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lagg0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=0
ether 8c:8c:aa:bd:bb:ef
hwaddr 00:00:00:00:00:00
inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255
laggproto failover lagghash l2,l3,l4
laggport: re1 flags=5<MASTER,ACTIVE>
laggport: wlan0 flags=0<>
groups: lagg
media: Ethernet autoselect
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

This is the output when not working on first boot:

re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
ether 8c:8c:aa:bd:bb:f0
media: Ethernet autoselect (none)
status: no carrier
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
re1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=80088<VLAN_MTU,VLAN_HWCSUM,LINKSTATE>
ether 8c:8c:aa:bd:bb:ef
inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
wlan0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=0
ether 8c:8c:aa:bd:bb:ef
hwaddr 70:9c:d1:af:ad:93
inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255
groups: wlan
ssid Smithies channel 40 (5200 MHz 11a vht/80-) bssid f0:9f:c2:ab:8d:c3
regdomain FCC country US authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit AES-CCM ucast:128-bit txpower 17
bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k
ampdudensity 8 -amsdutx amsdurx shortgi -ldpctx ldpcrx -uapsd vht
vht40 vht80 vht160 -vht80p80 wme roaming MANUAL
parent interface: iwlwifi0
media: IEEE 802.11 Wireless Ethernet VHT mode 11ac
status: associated
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lagg0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=0
ether 8c:8c:aa:bd:bb:ef
hwaddr 00:00:00:00:00:00
inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255
laggproto failover lagghash l2,l3,l4
laggport: re1 flags=5<MASTER,ACTIVE>
laggport: wlan0 flags=0<>
groups: lagg
media: Ethernet autoselect
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

I should note that running doas service netif restart once it's working makes it fail again.

Any ideas ??

Cool so QT6 was the issue when I ran doas pkg update and doas pkg upgrade yesterday. Today the QT6 version of Qutebrowser has now been built for #FreeBSD `15.0 Latest and it no longer tries to uninstall Qutebrowser. 😃

https://www.freshports.org/www/qutebrowser/

some days I wish upgrading #FreeBSD was as mindless as upgrading my #OpenBSD machines.

On OpenBSD, it's generally `sysupgrade`, let it do its thing, rebooting itself a couple times (entering my FDE passwords as necessary), and then a `pkg_add -u` to upgrade my packages. Sometimes a `sysmerge` if it can't do it automatically. But very much two (or three) idiot-proof commands with very little demand on this idiot's brain to recall where I am in the process.

While I like the automatic ZFS boot-environment snapshotting, FreeBSD requires me to know the next version-number I want to upgrade to (can't determine it or prompt me for viable options?), transcribe it as part of the upgrade command, then manually running `freebsd-update install` multiple times, rebooting manually multiple times between each, then `pkg update` and a `pkg upgrade` to update userspace. I'm sitting at a login…is this the first, second, or third reboot? I don't know, it was taking a while and I ended up wandering off to do something else.

This post brought to you by this morning's 14.3→14.4 FreeBSD upgrade 😆

I think I got it working now after remaking it lol
https://snac.9front.club/thedaemon
#snac2 #snac #FreeBSD

Hmmm Me thinks that #Waybar has a memory leak as normally it runs with 64Mb ram using my config and uses about 1.5% of the CPU's but after an hour or two it ramps upto 100% useage on all cores and ram useage goes into Gigs until I kill it and restart it. #Wayland #FreeBSD

My mistake it still says 0.11.0 on Github releases but 0.12.0 if you look in releases

https://github.com/DreamMaoMao/mangowc/releases

How has #FreeBSD got an update for #MangoWC V0.12.0 when on the official repository only V0.11.0 has been released !? 😦

https://github.com/DreamMaoMao/mangowc/releases/tag/0.11.0

https://www.freshports.org/x11-wm/mangowc/

Found the issue with screenshots on #MangoWC having random lines in them.
I have found out that it is caused by animations on the layerrule for slurp. Previously I had as per the docs:

layerrule=noblur:1,layer_name:selection

But have discovered if I also disable animations for slurp then it takes crystal clear screenshot selections now.

layerrule=noanim:1,noblur:1,layer_name:selection

https://mangowc.vercel.app/docs/window-management/rules#layer-rules

#FreeBSD #Linux

Make finding bugs in FreeBSD more expensive.

https://www.reddit.com/r/freebsd/comments/1trbgfd/comment/oomg93o/

Don't shoot the messenger.

#FreeBSD #bugs

After decades on #Linux, #FreeBSD finally gave me a reason to switch operating systems

https://www.newsbeep.com/nz/270060/

#Linux on notebook? Check ✅
(*Trying to set up #FreeBSD for daily driving? Check ✅)
No systemd distro? Check ✅
#CustomROM on phone? Check ✅
#Degoogled android? Check ✅
#OpenSource apps? Check ✅
#Fediverse? Check ✅
Am I missing something? :)

Default vm-bhyve template for #freebsd has 256MB RAM.

The installer dies silently trying to fetch pkgbase packages.

2GB works.

Keeping my streak: next daily source reading is up: https://blog.wollwage.com/2026/20260207-daily-source-reading-ed.html

#FreeBSD #OpenBSD

I'm about to give up on getting FreeBSD installed on my 9th Gen Lenovo X1 Carbon. No matter what I do or try, I simply cannot get the install to boot. I've tried many different ways. The ISO, the .img file, nothing works. Pretty straightforward hardware: 11th Gen Core i5, 16 GB or RAM, Intel Iris Graphics.

Anyone have any ideas or maybe experiencing this same issue?

#FreeBSD

Confirming a fix in FreeBSD 14.3-BETA3

https://www.reddit.com/r/freebsd/comments/1khf860/comment/mstkxfs/

#FreeBSD #Firefox #MATE #simple #elegant

I have asked for my #FreeBSD commit bit to be taken into safekeeping. It’s been a few years since I actually committed code to the repo (I still maintain libcxxrt and dtc, which are in the base system, so my code has been committed by others in that time).

This is the second time. I reactivated it a couple of years ago and wrote a qemufwcfg driver (split NetBSD-style between a simple kernel device and a FUSE filesystem), but the review comments put me off bothering to get it into the tree (someone else is welcome to do it if they want to pull it out of phabricator). I still occasionally do code review for other folks, feel free to keep tagging me for reviews.

Still a happy FreeBSD user. If I have FreeBSD time again (any decade now…) I hope to work more on container things. The Apple folks who did their container thing have said they’re happy to take patches to support FreeBSD containers. Their one-VM-per-container model makes this much easier than Podman, which assumes a single VM so is hard to transparently support both Linux and FreeBSD guests.

The only thing I’d like to do that I’d want to put in the base system is a more modern service management and eventing system. And I doubt I’ll have time to work on that for a few years.