Replied in thread
@sumerian Not to be confused with du(1), which shows you how MUCH you built or made. 
(du is a unix command that shows how much disk space the files in a directory are using).
man.freebsd.orgFreeBSD Manual Pages
Recent searches
Search options
#freebsd
69 posts58 participants8 posts today
This fortnight has been a catch-up of a month++ backlog on ports, to get these all in for the 14.3-RELEASE quarterly cycle:
- Elixir 1.18.4
- Erlang/OTP 28
- CouchDB 3.5.0, bump after OTP27
- RabbitMQ 4.1.0
- Crystal (take ownership)
- Shards (ditto)
- LavinMQ
- Aider.chat 0.83.0 + 3 update & add supporting ports
- Buildkite Agent
- Ansible Runner
- Anubis
- Graylog
- NS1-python
- streamlit
- Gleam
- esbuild
And that's just in a month. Other porters (e.g. KDE & GNOME teams, or rnagy@ who does firefox and various chromium ports) do even more, either timewise, and/or complexity wise.
You too can help! Even a *single port* if its one you use, and are familiar with, makes a huge difference.
Stop by in discord, IRC channels, mailing lists, and join in. The learning and accomplishment is all part of the fun!
A #reboot is a solution to many tech problems. But if you are on #Linux, did you know you need to reboot only if your kernel has changed? Otherwise you can do a "soft reboot" and get the same thing. You need to kill the init process and make it respawn. It varies from distro to distro but on #systemd ones, you can do systemctl soft-reboot and it'll do the job for you.
Also if you have problem with your graphical shell, you can simply restart your graphical stuff. Not even a soft reboot is needed. For instance if your display manager is lightdm like me, simply do systemctl restart lightdm.
I think this applies to other #unixlike operating systems with the similar kernel and system architecture as Linux. Maybe #BSD people can share their experience?
Reviewing log messages from one of my #FreeBSD servers, I am wondering what a valid hug would look like!
![web1 login failures:
May 27 03:30:09 web1 sshd[68939]: Invalid user hug from xxx.xx.xxx.xxx port 47462
May 27 03:30:09 web1 sshd[68939]: Disconnected from invalid user hug xxx.xx.xxx.xxx port 47462 [preauth]](https://files.mastodon.green/media_attachments/files/114/584/188/981/240/350/original/80c95378b4a8cd80.png "web1 login failures:
May 27 03:30:09 web1 sshd[68939]: Invalid user hug from xxx.xx.xxx.xxx port 47462
May 27 03:30:09 web1 sshd[68939]: Disconnected from invalid user hug xxx.xx.xxx.xxx port 47462 [preauth]")
Replied to Stefano Marinelli
@stefano Feeling the pain with #tailwindcss on OpenBSD. V3 was working with some fiddling but V4 broke again. It is pretty annoying to be honest.
The May 27th, 2025 Jail/Zones Production User Call is up:
We discussed building #FreeBSD with Packaged Base, RC dependence resolution with topo, potential Jail escapes, 'reboot' vs. 'shutdown -r now' behavior, the possibility of unprivileged Jail creation, and more!
"Don't forget to slam those Like and Subscribe buttons."
youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
New 𝗙𝗮𝗶𝗹𝗲𝗱 𝗕𝗮𝗰𝗸𝘂𝗽 𝗦𝗲𝗿𝘃𝗲𝗿 𝗕𝘂𝗶𝗹𝗱 [Failed Backup Server Build] article on my https://vermaden.wordpress.com/ blog.
https://vermaden.wordpress.com/2025/05/28/failed-backup-server-build/
Replied in thread
@Linux @rriemann @eu_os I’m not even saying “use NixOS as base”, I am saying use #Nix (the build tool) to build your own #NixOS sibling if you want. In theory one could even build an OS based on #FreeBSD (like Dell’s ThinOS) using a reproducible build tool like Nix (not how Dell does it I assume). This notion of “Linux distributions” is so entrenched but it’s the first dogma that crumbles when looking into Nix. It’s quite refreshing.
Take your FreeBSD ZFS game to the next level! 
In our latest blog, Benedict Reuschling dives into automated ZFS snapshots with Sanoid — a powerful tool to schedule, manage, and prune snapshots effortlessly on FreeBSD. Learn how to set up snapshot policies to keep your data safe.
Bonus: Includes a ready-to-go Ansible playbook!
Read now: https://freebsdfoundation.org/blog/zfs-automatic-snapshots-with-sanoid-on-freebsd/
#FreeBSD #ZFS #OpenZFS #SysAdmin #Sanoid #Snapshots #DataRecovery #Ansible
NEW VIDEO - Setting Up Jenkins CI on FreeBSD Was WAY Simpler Than I Thought!
#FreeBSD #Unix #Opensource #jenkins #garyhtech
https://youtu.be/Xeg5WvRXJ2A?si=D9-uA10rpdyd1wHd via @YouTube
youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
On #FreeBSD, the simple patching is sometimes overlooked. Don't.
sudo freebsd-update fetch install
sudo pkg upgrade
#syslog_ng 4.8.0 improved the wildcard-file() source on #FreeBSD and #MacOS. Version 4.9.0 will do the same for #Linux by using #inotify for file and directory monitoring, resulting in faster performance while using significantly less resources. https://www.syslog-ng.com/community/b/blog/posts/testing-the-new-syslog-ng-wildcard-file-source-options-on-linux
www.syslog-ng.comTesting the new syslog-ng wildcard-file() source options on LinuxLast year, syslog-ng 4.8.0 improved the wildcard-file() source on FreeBSD and MacOS. Version 4.9.0 will do the same for Linux by using inotify for file and directory monitoring, resulting in faster performance while using significantly less resources...
This morning's soundtrack:
https://www.youtube.com/watch?v=TpMzD8Q1fQg
Sipping coffee from Café du Monde (New Orleans - I have about 5 cans of it!)
Coming Soon: blog post by yours truly on running #Drupal on #FreeBSD on #ZFS with #bastilleBSD for managing the setup and configuration of the #jails
But for now... Work...
Continued thread
Interesting final note:
#FreeBSD/#NetBSD (and netkit-rwho) #rwhod uses the original "who" UDP port, 513.
There's a "new-who" UDP+TCP port, 550 and a "new" 224.0.2.1 multicast address. They have been in the assigned number list ever since RFC 1090, footnoted to Jon Postel and the "unofficial" BSD "rwho Group".
They've been reserved for 35 years, and I can find nothing to show for the efforts of whatever this "unofficial Group" was.
Continued thread
10. IPv6 exists.
11. fstatat() exists. You don't have to hardwire the private database location so you can get back there from chdir("/dev"). But anyway ...
12. You might not need a login database or /dev. The kernel has all of the info about current sessions, their terminals, and their setlogin() names, in memory, but just lacks a sysctl for reading it out.
Continued thread
Tool changes:
5. Follow UCSPI-UDP and UCSPI-TCP conventions, at minimum as an option. Let someone else with privileges open the socket.
6. Don't fork-and-exit. Allow simple logging to standard error. Let someone else have already dropped privileges and chdir()ed you. Permit proper process supervision.
7. --help
8. Allow the login database to be configurable, as a command line option or some such.
9. Permit a reduced mode where multiple terminals are squashed into one.
Continued thread
What lessons could the 21st century teach #FreeBSD #rwhod?
0. More modern cluster monitoring tools exist. But failing that ...
Protocol changes:
1. Encrypt broadcasts with a shared secret that is installed by sysops via sneakernet or something.
2. Use a client-server pull model. Send data only when an authorized client with the right shared secret (connects and) asks.
3. 8 characters stopped being long enough in the 1980s.
4. Use TAI64 timestamps.