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.
Here is a pro tip: Process substitution allows you to treat the output of a #Linux / #Unix command as if it were a file, or write output as if you were writing to a file, but have it piped into another command's input. It's handled by the shell like Bash or Zsh. Syntax:
<(command)
command1 <(command2)
Where you would normally put an input filename for a command, you can instead put <(some_other_command2)
PATH isn’t real on Linux
I have no idea how much relevance this short but informative rundown of how PATH works in Linux has in the real world, but I found it incredibly interesting and enlightening.
The basic gist - and I might be wrong, there's code involved and I'm not very smart - is that Linux itself needs absolute paths to binaries, while shells and programming languages do not. In other words, the Linu
https://www.osnews.com/story/142244/path-isnt-real-on-linux/
I'm trying to add "genric" #signal handling to #poser. Ultimate goal is to provide a way for #swad to handle #SIGHUP, although signal handling must be done in poser's main event loop (signals are only ever unblocked while waiting for file descriptor events).
Okay, I could just add explicit handling for SIGHUP. But a generic solution would be nicer. Just for example, a consumer might be interested in #SIGINFO which doesn't even exist on all platforms ... 🤔
Now, #POSIX specs basically just say signal constants are "integer values". Not too helpful here. Is it safe to assume an upper bound for signal numbers on "real world" OS implementations, e.g. 64 like on #Linux? Should I check #NSIG and, if not defined, just define it to 64? 🙈
I use Zip Bombs to Protect my #Linux and #Unix Server from AI and other stupid bots https://idiallo.com/blog/zipbomb-protection
@annaleen I use Zathura for viewing PDFs, which is available at least on Linux on Mac.
Besides not bundling AI, there's no toolbar: All you see is the PDF.
There are some intuitive key commands for basic functions like page up, page down. Because it's minimal, launches very quickly and makes the most of smaller screens, like laptops.
https://pwmt.org/projects/zathura
If you are looking to channel your anger with Adobe into action, there you go.
I wrote a book on Linux Memory Management, published by @nostarch - it's a comprehensive 1300 page exploration of Linux 6.0's memory management code, depth-first, diving into the code and REALLY explaining how things work.
The idea is to avoid hand waving as much as possible and literally explore what the kernel _actually_ does.
It's full of diagrams and careful explanations of logic including a ton of stuff you just can't find anywhere else.
It's currently available in its entirety in draft form via early access when you pre-order.
It's available at https://nostarch.com/linux-memory-manager
:)
Hi all you all know of me.
My name is Stu for anyone who hasn't heard of me.
I like technology and music and golf ⛳.
I love open source platforms and decentralized platforms.
Revisiting #async / #await in #POSIX C, trying to "add some #security" 🙈
Recap: Consider a classic #reactor-style service in C with a #threadpool attached to run the individual request handlers. When such a handler needs to do some I/O, it'll have to wait for its completion, and doing so is kind of straight forward by just blocking the worker thread executing the job until whatever I/O was needed completes.
Now, blocking a thread is never a great thing to do and I recently tooted about an interesting alternative I found: Make use of the (unfortunately deprecated) POSIX user context switching to enable releasing the worker thread while waiting. In a nutshell, you create a context with #makecontext that has its own private #stack, and then you can use #swapcontext to get off the thread, and later again to get back on the thread. A minor issue is: It must be the *same* thread ... so you might have to wait until it completes something else before you can resume your job. But then, that's probably okayish, you can make sure in your job scheduling to only use worker threads with awaited tasks attached when no other thread is available.
In my first implementation, I just used #malloc to create a 64kiB private stack for each thread job. That's perfectly fine if you can guarantee your job will never consume more stack space, AND it won't have any vulnerabilities allowing some attacker to mess with the stack. But in practice, especially for a library offering this async/await implementation, it's nothing but a wild #CVE generator.
So, I now improved on that:
* Allocate a much larger stack of now 2MiB. That alone makes issues at least less likely. And on a sane modern OS, we can still assume pages will only be mapped "on demand".
* Only allocate the stack directly before running the thread job, and delegate allocation to some internal "stack manager" that keeps track of all allocated stacks and reuses them, only freeing them on exit. This should avoid most of the allocation overhead.
* If MAP_ANON / MAP_ANONYMOUS is available, use #mmap for allocating the stack. That at least gives a chance to stay away from other allocations ....
* But finally, if MAP_STACK is available, use this flag! From my research, #FreeBSD, #OpenBSD and #NetBSD will for example make sure there's at least one "guard page" below a stack mapped with this flag, so a stack overflow consistently takes the SIGSEGV emergency exit 😆. #Linux knows this flag as well, but doesn't seem to implement such protection at this time ... 🤔
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟰/𝟮𝟴 (Valuable News - 2025/04/28) available.
https://vermaden.wordpress.com/2025/04/28/valuable-news-2025-04-28/
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/04/28) available.
https://vermaden.wordpress.com/2025/04/28/valuable-news-2025-04-28/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Interlude dans la projet de migration de VM sous #Proxmox, on fait de l'entretien hardware, et c'est tout de suite sur https://twitch.tv/ahp_nils ! #sysadmin #devops #twitchfr #twitchstreamer #TwitchStreamers #linux #patethermique
I would love to see more Linux desktop users, but people (mostly kids or gamers) who watch PewDiePie will not dump Windows because they want those AAA game titles and apps from Adobe and others unavailable on #Linux. Apps are the problem. I’ve been using Linux since the early days, and it is ready for many use cases, especially when privacy is your major concern. Otherwise, you should have the willpower to accept and learn alternative apps.
Regardless of PewDiePie’s personal #politics (which clearly, at the very least are problematic), it is fairly well known by anyone who has been following him for any number of years that the vast majority of his fan base are enthusiastic fascists.
Now #PewDiePie , who’s content centers around PC gaming and Windows, has decided to switch to #Linux and published a video encouraging his followers to do the same. This means a very large number of his #fascist fan base is going to be switching to Linux.
Now many Linux communities are going to be forced to more explicitly choose their politics. Like the parable of the Nazi bar, if the community remains politically neutral, it will become fascist in short order.
A few things to be wary of:
Investing in automation for #flatpak is an excellent idea!
Love to see this!
https://enblog.eischmann.cz/2025/04/25/hiring-for-flatpak-automation/
Client: The server is down! What happened?
Me: *types furiously* "Just a minor kernel panic. Don't worry, I'm fscking it back to life. Hold on..
Client: You're...fisking it?
If you ever accidentally end up inside vi or vim or neovim by reading some tutorials online, you can quit it by pressing Escape, colon ( : ), q (q), bang (!) and pressing return. It is simple as that. Modern version of VIM even tells you that on welcome screen. No need to panic.
Parallel ./configure for #Linux or #Unix: I paid good money for my 24 CPU cores, but ./configure can only manage to use 69% of one of them. As a result, this random project takes about 13.5× longer to configure the build than it does to actually do the build.
https://tavianator.com/2025/configure.html
@BoxyBSD was always for BSD based systems only. I focussed to push the whole BSD community and to encourage people to try BSD based systems (such like #FreeBSD. #NetBSD, #OpenBSD, etc.) but I'm not sure if it might provide more value to the whole #opensource community by also supporting #Linux systems (such like #Debian, #Ubuntu, #RockyLinux, #SuSe and more).
I'm not sure if the #BoxyBSD project still provides a value for the community right, now.
What do you think?
I have many old #Linux magazines. If you want them, and are willing to pick them up in #Delft let me know.
I put them also on Marktplaats:
* https://www.marktplaats.nl/seller/view/m2243370849
* https://www.marktplaats.nl/seller/view/m2261278516
* https://www.marktplaats.nl/seller/view/m2261550502
Free for #Mastodon users :-)
cc: @nllgg
Torvalds states the obvious: file systems should be case-sensitive
Apparently, the Bcachefs people are having problems with case-folding, and Linus Torvalds himself is not happy about it. Torvalds holds the only right opinion in this matter, which is that filesystems should obviously be case-sensitive.
Case-insensitive names are horribly wrong, and you shouldn't have d
The Linux mascot is a penguin named Tux because Linus Torvalds, the creator of the #Linux kernel, was bitten by a penguin. Seriously, he claims he didn't actually get sick, but it solidified his affection for them. This is the best origin story for a tech mascot ever. Happy World Penguin Day.
🌟 Introducing BSD.cafe 🌟
Excited to present the first building block of the BSD Cafe project! When I registered this domain months ago, I envisioned a themed bar where we can casually chat about *BSD systems, Linux, and Open-Source technology among friends, acquaintances, and patrons. But like any bar, discussions can cover a wide range of topics while respecting everyone.
BSD.cafe will be a hub for various tools and services, powered by *BSD.
The first brick is a new Mastodon instance, a gateway to the Fediverse. Registration is open, and the server will be moderated under clear guidelines promoting good behavior and zero tolerance for hate towards anyone. Inclusivity, respect, and constructive dialogue are the key values of this new instance.
The main server is currently hosted in Finland on a small VM, based on #FreeBSD. Services are divided into VNET jails, connected in a LAN via a local bridge. A VPN system is also present and have been able to move individual jails to different, more powerful, machines.
Multimedia data and cache are hosted on another physical server (FreeBSD, within a jail), with Cloudflare in front. The aim is to cache and geodistribute data, reducing network traffic on the main VPS.
Reverse proxy (frontend), mail server, media server, and the instance itself are reachable via #ipv6.
The instance started empty. No unnecessary content was pre-loaded; I want it to grow organically based on users' interests and following. There won't be any preemptive blocks at this stage. Users are encouraged to promptly report anything they find worth flagging.
Join us at https://mastodon.bsd.cafe to build a constructive and inclusive community—a safe and relaxing space for everyone.
Our wiki, located at https://wiki.bsd.cafe, features essential links and articles related to the BSD world. It provides an overview of the tools, services, rules, uptime, and more information about the BSD Cafe Services.
A Matrix server, a Miniflux RSS Reader, the Wiki itself, and the BlendIT Lemmy instance are all part of the BSD Cafe services, with more to come.
#BSD #OpenSource #Fediverse #Community #Tech #Networking #Mastodon #Inclusivity #FreeBSD #NetBSD #OpenBSD #DragonflyBSD #Linux #OSS #SysAdmin #Miniflux #RSS #Matrix
Strong suspicion I could swap out #macOS for #Linux, do better with #Minecraft and most everything else, and not do much worse at macOS-specific stuff like #GarageBand and Messages under #OSXKVM (https://github.com/kholia/OSX-KVM).
Anyone done this, or something similar?
nun sind es schon zwei Amazon-Fire-TV Geräte, die hier ausgemustert rumliegen.
eines ca. 11 Jahre alt, ein Fire-TV Kasterl der zweiten Generation (glaube ich, noch mit LAN-Buchse), und ein ca. 9 oder 8 Jahre alter TV-Stick.
Ob das noch lohnt, die zu Jailbreaken und ein natives #Android oder anderes #Linux drauf zu packen? #amazon #firetv
EU OS: A European Proposal for a Public Sector Linux Desktop: https://thenewstack.io/eu-os-a-european-proposal-for-a-public-sector-linux-desktop/ via @TheNewStack & @sjvn
There's nothing official about it yet, but this Fedora #Linux/KDE immutable distro plan is starting to gain traction.
Linus Torvalds has coded git two decades ago.
Learn about why how who and where here
https://youtu.be/sCr_gb8rdEI?si=s8tDVh1e8dBTGWkJ
🖋️ #bash #sh #zsh #ksh #csh #tcsh #fish #git #Linux #POSIX #FOSS #100daysofCode #640DaysOfCode #coding #1024DaysOfCode #github #programming