Search

Items tagged with: openbsd


@rl_dane @fbievan @amin

Don't use rc.local. It has been obsolete since 1983. #FreeBSD has actually discontinued it twice in its history.

FreeBSD has had Mewburn rc for most of this century. It's what #NetBSD uses and #OpenBSD has a similar but NIH system. At minimum, use Mewburn rc scripts.

jdebp.info/FGA/rc.local-is-his…

The rc(8) manual page has an example script. There's tutorial doco as well.

docs.freebsd.org/en/articles/r…

#rc #MewburnRC



BorgBackup 1.4.3 was just released!

This is primarily a bugfix release, the Linux and FreeBSD binaries built on Github now have working FUSE support (borg mount).

Our CI testing now includes *BSD and Haiku OS!

github.com/borgbackup/borg/rel…

#borgbackup #linux #freebsd #openbsd #netbsd #macos #haiku



And oh boy all terms seem so foreign to me as a long time #Linux user. The same disk is called ada0 with a partition like ada0p2 in #FreeBSD, will be called something like sd0 with sd0h in #OpenBSD, ld0 and dk2 in #NetBSD . Then to experiment, all the #dkctl, #disklabel and #fdisk commands are like blue and red wires on a dynamite you have to get rid of 😱. Linux distros nowadays seem to be going to the #gdisk way which feels very much like #gpart in FreeBSD.
#UseBSD #RUNBSD #BSD #FOSS #UNIX #Linux




@ebassi I don't use Gnome and I'm still in #X11 land on #OpenBSD and my #MLVWM window manager, so I'm just "thinking out loud" here...

Do Gnome apps reliably "do the right thing" if sent a SIGTERM, e.g. confirming quit and/or prompting to save unsave changes, as necessary? If so, maybe write a script (triggered on super-q) to get the PID for the frontmost window's process and then `kill -TERM -p $PID` it?



First steps in the BSD world!

1) OpenBSD on VPS (Amsterdam)
2) FreeBSD on Raspberry Pi 4 (home)

I'm running a Wireguard connection between the two.

Next step is setting up relayd on the VPS to point at services on the Raspberry Pi server.

#OpenBSD #FreeBSD #selfhosted




Dear friends of the BSD Cafe,

As 2024 comes to an end, it’s time to reflect on what we’ve built together during the first full year of life for BSD Cafe. Launched on 20 July 2023, this project has grown far beyond what I could have imagined. While I haven’t tracked full uptime data, I can confidently say that the downtime was less than 30 minutes overall - even though the main VM hosting our services moved multiple times (including a switch from a Proxmox hypervisor to bhyve on FreeBSD, for the sake of alignment with our mission). In a world filled with over-engineered HA systems, we’ve outperformed many “big-name” cloud providers. Not bad for a community project, right?

For me, this has been an incredible journey. The users here are not just participants - they’re collaborators, and their positivity has been inspiring. The content shared and created at BSD Cafe has been valuable not only to the BSD community but beyond. What truly sets BSD Cafe apart is the openness for dialogue and exchange. Whether it’s social media posts, Matrix discussions, repositories in our brew, or RSS feeds, people seem to genuinely appreciate what we create and the conversations we foster.

BSD Cafe is a journey - one that grows, evolves, and continues. Our goal isn’t endless growth (we’re a community, not a business) but rather to maintain a welcoming, inclusive space where everyone feels a sense of positivity and belonging. For me, opening any service with “bsd.cafe” in the domain brings joy and pride. That’s the spirit I’ve tried to convey, and I hope it resonates with all of you, whether you’re active BSD Cafe users or friends of the community.

Promoting self-hosting and #OwnYourData has, as a side effect, inspired some users to “go solo” with their own setups. But even then, they remain part of BSD Cafe - in spirit, in purpose, and in connection.

Here’s a look at what we’ve achieved together this year:

- mastodon.bsd.cafe: 370 total users
Active in the past month: 207
Active in the past six months: 286
- snac.bsd.cafe: 14 total users
Active in the past month: 7
- blendit.bsd.cafe: 61 registered users
- matrix.bsd.cafe: 23 users
- brew.bsd.cafe: 29 users - 80 repositories
- freshrss.bsd.cafe: 25 users
- miniflux.bsd.cafe: 11 users
- press.bsd.cafe: 9 users
- myip.bsd.cafe: Constantly used by various users
- wiki.bsd.cafe: Could use a bit more love and content, but it fulfills its role as a functional homepage.
- tube.bsd.cafe: Still in testing - Peertube 7.0 update is on the way.

For detailed stats from our reverse proxy and general router (excluding media services, which generate most traffic but are handled via caching reverse proxies), you can check here - updated hourly: netstats.bsd.cafe

The journey of BSD Cafe continues, and I look forward to seeing where 2025 will take us. Together, we’ve built something special - something driven by passion, shared purpose, and a little bit of the BSD magic that makes all of this possible.

Here’s to a new year full of joy, serenity, and connection. Thank you for being part of this adventure.

Wishing you all a fantastic 2025 - and THANK YOU!
Stefano

#BSDCafe #BSDCafeServices #BSDCafeAnnouncements #BSDCafeUpdates #Fediverse #HappyNewYear #Mastodon #Snac #snac2 #lemmy #matrix #dokuwiki #forgejo #freshrss #miniflux #wallabag #peertube #FreeBSD #OpenBSD #NetBSD #RunBSD #BSD


If you are on #OpenBSD or #FreeBSD and you're still seeing issues with extravagant memory use on this release candidate, please let us know :) Initial reports seem to indicate that the issue is resolved but we'd like to know for real before we call it fixed and move on to cutting 0.17.0 proper. Thanks!