Plasma visually bugged following an upgrade on FreeBSD
https://www.reddit.com/r/kde/comments/1lne10b/plasma_visually_bugged_following_an_upgrade_on/
Dear #FreeBSD users,
What shell(as in text shell in the Terminal) do you use?
Best Regards,
Farooq the Chickenkiller.
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...
Dear friends of the BSD Cafe,
This idea has been in my mind since the very beginning of this adventure, almost two years ago. Over time, several people have suggested it. But until recently, I felt the timing just wasn’t right - for many reasons. Today, I believe it finally is.
So I’m happy to announce a new service:
The BSD Cafe Journal - https://journal.bsd.cafe
At first, I thought I’d use BSSG for it (I even added multi-author support with this in mind), but in the end, it didn’t feel like the right tool for the job.
The idea is to create a multi-author space, with content published on a fairly regular basis. A reference point for news, updates, tutorials, technical articles - a place to inform and connect.
Just like people in Italy used to stop by cafes to read the newspaper and chat about the day’s news, the BSD Cafe Journal aims to be a space for reading, sharing, and staying informed - all in the spirit of the BSD Cafe.
What it’s not:
It’s not here to replace personal blogs, or excellent newsletters like @vermaden 's. And it’s not an aggregator.
What it is:
A place where authors can write original content, share links to posts on their own blogs or elsewhere, publish guides, offer insights, or dive into technical explanations.
The guiding principles are the same as always: positivity, constructive discussion, promoting BSDs and open source in general. No hype (sharing a cool new service is fine, posting non-stop about the latest trend is not), no drama, no politics. The goal is to bring people together, not divide them. To inform, not inflame.
Respect, tolerance, and inclusivity are key. Everyone should feel welcome reading the BSD Cafe Journal - never judged, offended, or excluded.
The platform I’ve chosen is WordPress, for several reasons: it’s portable (runs well on all BSDs), has great built-in role management (contributors, authors, etc.), and - last but not least - supports ActivityPub.
This means every author will have their own identity in the Fediverse (like: @stefano ) and can be followed directly, and it’ll also be possible to follow the whole Journal.
Original and educational content is encouraged, but it’s also perfectly fine to link to existing articles elsewhere. Personally, I’ll link my technical posts from ITNotes whenever I publish them there.
The goal is simple: a news-oriented site, rich in content, ad-free, respectful of privacy - all under the BSD Cafe umbrella.
Content coordination will happen in a dedicated Matrix room for authors. There’ll also be a public room for discussing ideas, giving feedback, and sharing suggestions.
Of course, I can’t do this alone. A journal with no content is just an empty shell.
So here’s my call for action:
Who’s ready to lend a hand? If you enjoy writing, explaining, sharing your knowledge - the Journal is waiting for you.
#BSDCafe #BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements #RunBSD #FreeBSD #NetBSD #OpenBSD #illumos #Linux #OSS #OpenSource #BCJournal #BSDCafeJournal
We’ve been thinking — what if there was a structured course to help more people learn how to use and contribute to FreeBSD?
Whether you’re just getting started or looking to sharpen your sysadmin skills, we’d love your input:
Would a FreeBSD course be useful to you or your team?
Your feedback could help shape future resources for the community.
#FreeBSD #OpenSourceLearning #TechTraining #FreeBSDFoundation
FreeBSD: preferring ee (avoiding vi) for csh/tcsh and sh
https://gist.github.com/grahamperrin/be1bc6ac40bfef0693b0ab5cef050f3e
ee(1)
https://man.freebsd.org/cgi/man.cgi?query=ee&sektion=1&manpath=freebsd-release
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login window
https://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
I need a Debian VM for the tech edits on #n4sa2e. Switched to the Mac, so I need to set up a new one.
Reminded once again that you can 95% set up a working Linux box by hitting ENTER in the installer. The only things you type are your username, passwords, and one TAB to say "yes, fry my disk." The advanced options are there, but you must look for them.
My #freebsd people: I love y'all, but THIS is an installer that welcomes new users.
Using pkgbasify to repair a broken installation of FreeBSD 14.3-RELEASE
https://gist.github.com/grahamperrin/9570092c127bd43777961b6f016e75ba
FreeBSD package repository name changes
https://reddit.com/r/freebsd/comments/1n40dbd/freebsd_repository_name_changes/
Help, please:
https://lists.freebsd.org/archives/freebsd-current/2025-September/008892.html
I want to use uclcmd with a file that is initially empty:
/usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD: pkgbase: major upgrades
― a rough guide, for alpha testing on AMD64.
From <https://redd.it/1nlo8lp>:
❮ An obvious response to the roughness: it's more complicated than legacy freebsd-update(8) (for FreeBSD 14.3-RELEASE). True; this is for alpha testing.
Please read the preamble before anything else. If you have any question, please don't hesitate to ask. ❯
@ax6761 bonjour! Ici Graham P, rapporteur du bug 287569.
Royaume-Uni, deux points:
1/ il y a quelques mois, FreeBSD developers ont fait beaucoup topnotch invisible changes, without which it would have been presque impossible to not only make a "PR" (not to be confused with une pull request) mais aussi trouvez un travail-around
2/ the pictured error peut etre moins likely to occur if requirements de la systeme sont documented
3/ mon "BR" (bug report, not to be confused with une probleme report) pour documentation n'etait pas acceptable.
Oh la la. Deux ou trois. J'suis un poet et I don't know it.
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287722>
― Website: system requirements: memory/RAM: UFS and ZFS
![Avatar for Farooq | فاروق [Master Patata]](/proxy/identity_icon/427100639409838458/72b327fba6.png){kind=icon}
