Search results for tag #freebsd
I remember when I started messing around with Linux, it all seemed so hard and Arch Linux was the big bad bogeyman.
Now, years later, I use Arch Linux as my daily driver, and I am starting to learn FreeBSD. Curiously, I don't find FreeBSD to be as intimidating as Arch Linux seemed to be wayback then. However, it is a beast I want to tame. I am getting my ass kicked at every twist and turn. 🤣
Slides have been released on this wonderful piece of balancing software for your proxmox clusters proxyLB
Now you can learn even more about this piece of wonderful software
Courtesy of @gyptazy
🖋️ #bash #proxyLB #freeBSD #boxyBSD #sh #zsh #ksh #csh #netBSD #openBSD #POSIX #proxmox #loadbalancer
https://github.com/gyptazy/ProxLB
Alt...
The screenshot is of a mobile application interface, likely a version control system like GitHub. At the top, the time is displayed as 10:34, the temperature is 27 degrees, and the battery is at 94%. The username "gyptazy" is visible, followed by the repository name "ProxLB." The main image features a graphic of two server racks labeled "Prox LB" with a conveyor belt and a small truck on it, set against a background of binary code. Below the image, there is a warning message in a yellow triangle with an exclamation mark, stating "Important: ProxLB 1.1.x is coming." The message explains that the repository is under heavy work and changes, which may result in issues, non-working pipelines, or incorrect documentation. It advises selecting a stable release tag for a suitable version during this time. The interface also shows one open pull request.
#RunBSD #Wayland #WindowManager
Been juggling hardware, moving VMs and jails around, and I shoehorned myself into a bit of an odd situation.
I had two Intel NUCs, one is a weaker Celeron CPU, with a meager 4 GB ram. The other is a beast with a much better CPU and 32 GB of ram.
The one with the 32 GB and strong CPU has the easy job, and the weak one has the hard job.
The easiest solution was to swap their drives, and network cables.
The only software change I had to make?
sed -i bak s/re0/em0/g /etc/rc.conf
on the first one
and, shocker.....
sed -i bak s/em0/re0/g /etc/rc.conf
That was _it_. Both systems came up clean because the #FreeBSD network subsystem isn't a clusterfuck.
That doesn't work in Linux.
@justine
I recommend reading this evident provocation.
http://xahlee.info/linux/why_tiling_window_manager_sucks.html
At the moment I am happy with #labwc.
I have configured the titlebar with double left click to iconify and middle click to close, xfce4-panel as vertical #deskbar with intelligent autohide.
I use "Run or Raise" with single key shortcuts for most used application.
Here is a link to an old implementation request of mine.
https://github.com/labwc/labwc/issues/673
Below is the current state of my #FreeBSD desktop environment
#FreeBSD Hello FreeBSD-nauts. As a FreeBSD newbie, I run into all kinds of little issues with my PC quite frequently to be honest.
Today, as usual, is not a big deal, but it is annoying as hell. I cannot get the volume knob in my Keyboard to work.
Help please! Thanks!
@thedaemon Well, #FreeBSD 15 exists ever since stable/14 was first branched. And you could trivially say it's "out", after all, everything happens in public. It isn't *released* yet of course.
Hmmm, on a #FreeBSD 14.2 host, running a 14.1 jail, is there any reason that 14.1 jail could not run a 14.2 jail?
I already run jails in jails...
#FreeBSD
Alt...
no
Alt...
no
@dave I feel ya pal. I was there at the “liquidate Steven’s favorite computer company for cash and return it as shareholder value” moment in 1997 and loved their climb and leap at the iPhone moment. I just bought a new mini, but i’m more excited by my #freebsd box (a 12 y/o Dell), @interlisp, #retrocomputing or my memories of the Aqua moment: https://stevengharms.com/posts/2025-01-04-return-of-aqua/
Signal Messenger client for terminal
https://www.freshports.org/net-im/gurk-rs/
In less than 2 hours, I created and put in production 3 new FreeBSD servers - each one with haproxy, nginx, mariadb, etc. - backups and monitorings included.
I created a set of jails then cloned them. Then customised them.
Those setups will run for *years* with some updates as they're meant to be stable and reliable.
Now, I can have another coffee and relax for some minutes 🙂
Dear #FreeBSD users,
What shell(as in text shell in the Terminal) do you use?
Best Regards,
Farooq the Chickenkiller.
@justine I love me some Collectd and MQTT. I haven't got a home assistant server though. (nor, in fact, NUT, anywhere, yet.) I decided Graphite and Grafana were too big and that I wanted to cobble up some graph thing that #Emacs eww or Dillo could browse. But right now I'm trying to replace #OpenWRT with some #FreeBSD jails. OPNsense would make more, um, sense, but I feel zany!
At the moment I'm showing the following:
CPU's 0-3 temperatures
Memory used
Uptime since last boot
WAN PPPoE Status
OPNsense Integration Updates Available
WAN IN/OUT graphs
LAN IN/OUT graphs
OSDay 2025 - Why Choose to Use the BSDs in 2025
There was limited time, so I couldn't go into much detail and had to keep things more general and structured than usual. I was also a bit nervous because of that — and honestly, it wasn’t my best performance. My English was pretty bad too.
https://it-notes.dragas.net/2025/03/23/osday-2025-why-choose-bsd-in-2025/
#RunBSD #FreeBSD #OpenBSD #NetBSD #DragonFlyBSD #HardenedBSD
Some time ago I wrote about using Helix editor on FreeBSD. I liked the „batteries included“ approach and I was curious to see whether Helix could be an actual replacement for Neovim.
I really tried and I forced myself to like Helix. And yes, Helix’s approach might be perfect for newbies who have never worked before with vim. But at some point I found myself on a customer’s server, desperately pressing ‚d‘ and wondering why it didn’t delete the character under my cursor. At this point I decided to dump Helix. The fact that some commands are slightly different, but not completely, made it hard for me to switch between systems and made me look like a complete idiot when editing a config while sharing the screen with a client.
BTW is there meanwhile an option to run lua-language-server on FreeBSD? I am using kickstart with nvim and it’s complaining that it can’t install the lsp because it’s not supported on this platform.
Now that it's official, I can announce it - although I may have dropped a few hints earlier! 😉
My talk "Why (and how) we’re migrating many of our servers from Linux to the BSDs" has been accepted, and I’ll be honored to present it in June at BSDCan in Ottawa.
The joy of meeting BSD friends in person again (and those I haven’t had the chance to meet live yet) will be immense, and the honor of sharing my story in Canada is truly beyond measure, especially considering the level of other talks and all the people attending.
Of course, I’ll be bringing various BSD Cafe gadgets with me!
For more information, here’s @mwl 's post with further details: https://blog.bsdcan.org/2025/03/18/bsdcan-2025-talks-tutorials-and-registration/
The FreeBSD team conquered a massive 7,000 bug backlog 💪 Once overwhelmed by thousands of open issues, the team, with the help of data visualization tools, turned chaos into clarity.
Their approach involved setting up custom dashboards using GrimoireLab, which provided valuable insights into their Bugzilla system. They introduced new metrics like "unattended" and "abandoned" tickets to prioritize their efforts.
Check out their full blog post: https://freebsdfoundation.org/blog/from-chaos-to-clarity-how-we-tackled-freebsds-7000-bug-backlog/
Mastodon will no longer support Redis Namespaces. The reasons are fully valid. Redis (or, more specifically, Valkey or KeyDB) is lightweight software that is easy to install/manage, so separation is always a good thing.
However, I read that many admins will face problems because they use Redis "in the cloud" and, therefore, have a single instance. Unfortunately, this is also a side effect of the "cloud," meaning the loss of control over your own software.
On FreeBSD, a thin jail with "Redis" takes up very little space and resources.
#OwnYourData – in the long run – always pays off.
So since 2004 #FreeBSD has a security system called "ugidfw" or "firewall-like access controls for file system objects" where you apply firewall like rules to permit or deny uid:gid to specific directories or files.
For example I could say:
add subject uid 22 gid 22 object uid 0 gid 0 filesys / type r mode r;
and then SSHD could only ever be able read regular files owned by root:wheel but never write them, etc.
It's a great way to detect with applications are trying to do strange things with permissions you are not expecting.
But it is a huge pain to debug problems, there are basically no guides or how-to examples. I keep meaning to write something up, but before I do is anyone aware of or interested in ugidfw?
#HomeLab #RunBSD #FreeBSD
Alt...
A screenshot of my N100 NUC OPNSense health page showing the CPU temperature graph and a 15C difference drop when a cooling fan was added.