schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
@volkerdi In celebration of Pride Month, and as a queer slacker myself, I quickly made this in GIMP. Now all the LGBTQ+ Slackware users can have a cool logo.
What you think? Pretty cool huh? :-)
Solved! ๐ฅณ
This was a pretty "interesting" bug. Remember when I invented a way to implement #async / #await in #C, for jobs running on a threadpool. Back then I said it only works when completion of the task resumes execution on the *same* pool thread.
Trying to improve overall performance, I found the complex logic to identify the thread job to put on a pool thread a real deal-breaker. Just having one single MPMC queue with a single semaphore for all pool threads to wait on is a lot more efficient. But then, a job continued after an awaited task will resume on a "random" thread.
It theoretically works by making sure to restore the CORRECT context (the original one of the pool thread) every time after executing a job, whether partially (up to the next await) or completely.
Only it didn't, at least here on #FreeBSD, and I finally understood the reason for this was that I was using #TLS (thread-local storage) to find the context to restore.
Well, most architectures store a pointer to the current thread metadata in a register. #POSIX user #context #switching saves and restores registers. I found a source claiming that the #Linux (#glibc) implementation explicitly does NOT include the register holding a thread pointer. Obviously, #FreeBSD's implementation DOES include it. POSIX doesn't have to say anything about that.
In short, avoiding TLS accesses when running with a custom context solved the crash. ๐คฏ
this is the most brutal tech job interview process Iโve ever read for most popular #linux distro ๐ฑ
https://dustri.org/b/my-experience-with-canonicals-interview-process.html
Latest ๐ฉ๐ฎ๐น๐๐ฎ๐ฏ๐น๐ฒ ๐ก๐ฒ๐๐ - ๐ฎ๐ฌ๐ฎ๐ฑ/๐ฌ๐ฒ/๐ฌ๐ฎ (Valuable News - 2025/06/02) available.
https://vermaden.wordpress.com/2025/06/02/valuable-news-2025-06-02/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Latest ๐ฉ๐ฎ๐น๐๐ฎ๐ฏ๐น๐ฒ ๐ก๐ฒ๐๐ - ๐ฎ๐ฌ๐ฎ๐ฑ/๐ฌ๐ฒ/๐ฌ๐ฎ (Valuable News - 2025/06/02) available.
https://vermaden.wordpress.com/2025/06/02/valuable-news-2025-06-02/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Added ๐จ๐ฃ๐๐๐ง๐ ๐ฏ - ๐ ๐ผ๐ฟ๐ฒ ๐ง๐ฟ๐๐ฒ๐ก๐๐ฆ ๐ฆ๐๐๐๐ ๐๐ถ๐ป๐๐ ๐๐ฟ๐ฎ๐บ๐ฎ to the ๐ง๐ฟ๐๐ฒ๐ก๐๐ฆ ๐๐ข๐ฅ๐ ๐๐ฒ๐ฟ๐๐๐ ๐ง๐ฟ๐๐ฒ๐ก๐๐ฆ ๐ฆ๐๐๐๐ article.
https://vermaden.wordpress.com/2024/04/20/truenas-core-versus-truenas-scale/#truenas-drama
#freebsd #freenas #truenas #linux #openzfs #server #trueos #debian #zfs #ubuntu
๐ maybe you can get help to turn your Windows 10 thing into something better:
#linux #windows10
Follow @Endof10 https://floss.social/@Endof10/114584759101866642
My grandpa finally moved from Ubuntu to Linux Mint. He says he 'upgraded to the greener version.' He genuinely thinks he's being tech-savvy (but I think he just wants to annoy me using words like 'Green Ubuntu'). I just nod and try not to correct him. LMAO. #LINUX #OpenSource #grandpa
Flatpak โnot being actively developed anymoreโ
At the Linux Application Summit (LAS) in April, Sebastian Wick said that, by many metrics, Flatpak is doing great. The Flatpak application-packaging format is popular with upstream developers, and with many users. More and more applications are being published in the Flathub application store, and the format is even being adopted by Linux dist
https://www.osnews.com/story/142467/flatpak-not-being-actively-developed-anymore/
I mean, #ChrisBarnatt from #ExplainingComputers literally makes easy-to-digest content (and for those that prefer/have to use reading over watching and/or listening there are writeups everywhere!) going over #migrating from #Windows to #Linux.
@lemgandi that's just Chris Barnatt who does gloss over things in a noob-friendly way.
"#Linux" is literally the #OS equivalent of a #Diesel engine as it's customizeable and resizeable from a single cylinder tiny unit that has less displacement than a pint to a giant heavy fuel oil ship diesel who's displacement is measured in cubic meters and everything in between.
(Some folks will say #NetBSD is a two-stroke becaise it can be made to run on anything!)
@happyborg And this just this week I decided to research why a nice mic, a Blue Yeti, quit working with Arch #Linux. It hadn't worked for more than a week.
I went through several troubleshooting steps only to find that at that moment, it had started to work again.
I have a new #Linux laptop. I have new Bluetooth headphones. But they frequently donโt connect.
This is an inconvenience for me but a critical failure for #blind users.
So I appreciated this rant and hope it spurs progress.
โI Want to Love Linux. It Doesnโt Love Me Back: Post 2 โ The Audio Stack Is a Crime Scene โ firebornโ https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-2-the-audio-stack-is-a-crime-scene/
OpenSUSE Tumbleweed doesnโt enable automatic snapshots in the home directories by default. I enabled them myself and noticed that, from time to time, the computer would completely freeze.
After some research, I discovered that Btrfs has this issue when quotas are enabled. I disabled quotas and the problem went away - although now the system probably doesn't know how much space each snapshot takes.
FreeBSD on my (old) desktop and ZFS - any snapshots I want, on much older (2018) and more limited hardware - and Iโve never seen anything like that happen.
The SSH protocol contains a hidden "haiku mode" (`ssh -H`):
ssh -H -l user ec2-server-ip-address
If activated, all #Linux/#UNIX server messages are returned in perfect 5-7-5 syllable structure. Debugging becomes very poetic ๐คญ
Youโve seen my posts about Linux accessibility. Youโve read me scream about broken screen readers, unusable bootloaders, and the sheer volume of stuff that only works after three undocumented hacks and a blood sacrifice. Thatโs from someone who already knows how to deal with this mess.
But what happens when someone new tries to step in?
My partner just published the first post in a new blog series called โLinux: Helpful or Headache?โ Itโs a personal account of what it feels like to stare into the abyss of Linux as a blind user who hasnโt even installed it yet. This isnโt a โhow toโ guide. Itโs not a technical tutorial. Itโs a moment of honest vulnerability and curiosity in the face of a system thatโs infamous for treating newcomers like an inconvenience.
Part One โ An Introduction
https://reading4life.mataroa.blog/blog/linux-helpful-or-headache-part-one-an-introduction/
Sheโs totally blind. Sheโs used to Windows and iOS โ platforms where accessibility is at least visible, documented, and supported. Linux? From the outside, it looks like a twisted obstacle course: too many distros, zero onboarding, no centralized help, and a community that can't agree on anything except that "you should have read the wiki."
And yetโฆ sheโs jumping in anyway.
This first post talks about that pre-installation limbo. The โwhat the hell even is a distro?โ stage. The existential dread of picking between MATE and GNOME when you donโt even know how to pronounce โFlatpak.โ The raw, unfiltered feeling of not knowing what you donโt know โ and doing it anyway, because the itch to explore is stronger than the fear of breaking stuff.
Thereโs no cheerleading here. No โyay open source!โ No tidy beginner tutorial with copy-paste terminal commands. Just one blind woman staring down the reality that Linux doesnโt come with a support number, and deciding to try it anyway โ not because itโs easy, but because she wants to learn, grow, and maybe even call bullshit where itโs due.
And if you're wondering โ no, I didnโt write or co-write it. This is her voice, her experience, her story. But it does tie in beautifully with the nightmare Iโve been chronicling in my own posts, from a totally different vantage point.
If youโve ever tried to onboard someone to Linux, especially someone disabled, this is what it actually looks like. And if youโve ever told someone โLinux is great, just pick a distro,โ read this and realize how much we take for granted.
Go read it. Boost it. Follow the series. She's only just getting started.
#Linux #Accessibility #FOSS #DisabilityInTech #Blind #NewUserExperience #Debian #UX #TechBlog #DigitalInclusion
npm error code EBADPLATFORM
npm error notsup Unsupported platform for @shopify/create-app@3.80.7: wanted {"os":"darwin,linux,win32"} (current: {"os":"freebsd"})
npm error notsup Valid os: darwin,linux,win32
npm error notsup Actual os: freebsd
We fought for years supporting Linux because we wanted to be "free to choose our OS", and now we've reached the point where you're forced to choose it.
Many people simply don't understand the concept of freedom.
Anyway, happy Wednesday!