linux

Debian adds an SPF record to debian.org https://lobste.rs/s/s1yqiu #email #linux
https://lists.debian.org/debian-devel-announce/2026/04/msg00010.html

"Linux lays down the law on AI-generated code, yes to Copilot, no to AI slop, and humans take the fall for mistakes — after months of fierce debate, Torvalds and maintainers come to an agreement"

"After months of fierce debate, Linus Torvalds and the Linux kernel maintainers have laid down the law on AI-generated code."

https://www.tomshardware.com/software/linux/linux-lays-down-the-law-on-ai-generated-code-yes-to-copilot-no-to-ai-slop-and-humans-take-the-fall-for-mistakes-after-months-of-fierce-debate-torvalds-and-maintainers-come-to-an-agreement

#Linux

Actually I #RunBSD because setting up audio in #Linux is too complicated.

Ik, 43-jaar oude #autist , zoek een baan want UWV wil me aan het werk hebben.

Ik zou niet weten hoe. Ik zou niet weten waar. Ik zou niet weten wat dan.

Ik zit al sinds 2007 thuis. Maar goed, ik ben nu aangemeld bij "jados" die een maandenlange wachtlijst heeft.

Heeft iemand ideeën of mogelijkheden in de regio #Rotterdam ?

Ik heb affiniteit met computers, en kan deze ook opbouwen. Verder #Linux en andere #FOSS oplossingen.

Alles is bespreekbaar.

#Baan #FediHire #Nederland

I’ve been running Linux off and on for years. But with a break from any meaningful experimentation since I bought my Steam Deck, I decided it was time for something new.

So I did the cliché thing and bought a used Thinkpad on eBay to install Linux on. Here’s my initial experience, with some backstory about my journey until now.

#linux #thinkpad #debian #fedora #bazzite #bluefin #pikaos #vanillaos
https://thumbsup.me/posts/i-put-linux-on-a-thinkpad/

That's a hate crime. ❌

#linux #gaming #windows #steamdeck

🖨️

My new printer stopped working under #LinuxMint the other day. Re-adding it resulted in a general error message.

Finally found the solution:

In the printer's "location" field, I had specified "Mein Büro" ("My office" in German). And Cups does not like umlauts in that field. 😶

After removing the "ü", the printer worked.

Maybe this information will be helpful to someone, at some point. 🙂

#printer #linux #cups #problemSolving #debugging #umlaut

Copy Fail - From Pod to Host https://lobste.rs/s/iy258n #linux #security
https://xint.io/blog/copy-fail-pod-to-host

Broadcasting GPS on the local network by @evert https://lobste.rs/s/4n38xw #linux
https://evertpot.com/broadcasting-gps-on-local-network/

Presenting Fedora Linux 44!

This release brings @gnome 50, @kde Plasma 6.6, tweaks to the Anaconda installer, and more!

Thank you to all of the contributors for another successful release. We hope you enjoy it!

➡️ https://fedoramagazine.org/announcing-fedora-linux-44/

#Fedora #Linux #OpenSource #GNOME #KDE

A daily #Linux command from #LinuxLexiconBot:

ilbmtoppm (1) - convert an ILBM file into a portable pixmap

I am a human, but my little bot posts a random Linux command daily. If you don't want to see it you can mute the LinuxLexiconBot hashtag.

Happy hacking!

[2022] the tragedy of gethostbyname https://lobste.rs/s/v1hrs7 #linux #networking
https://ariadne.space/2022/03/26/the-tragedy-of-gethostbyname.html

How cross-thread double free detection could work in glibc malloc https://lobste.rs/s/bb8f7o #c #linux #security
https://kallus.org/blog_tcache_key.html

It's been a while since I posted here, and at this point all of my previous posts have auto-deleted. Might as well reintroduce myself.

I am Gabriel, and I am based in Costa Rica. I work as an independent software developer and systems administrator.

As of late, my computer interests lie in #selfhosting, #Linux, and #containers. I care a lot about #privacy and ownership of our data and devices.

I am also passionate about #permaculture, #reading, #cycling, #fermentation, and #synthesizers.

Logic bug in the Linux kernel's __ptrace_may_access() function (CVE-2026-46333) https://lobste.rs/s/nwdn3w #linux #security
https://cdn2.qualys.com/advisory/2026/05/20/cve-2026-46333-ptrace.txt

Added some follow-up observations to my notes about Transparent Huge Pages (THP) on modern desktop Linux systems.

After ~1 week using:

[always] madvise never

on Slackware-current with Firefox-heavy workloads:

- no swap usage
- no THP fallback allocations
- no compaction stalls
- stable desktop responsiveness

Modern kernels appear to handle THP significantly better than older Linux generations, especially on systems with enough RAM, zram, and NVMe storage.

Notes:
https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Transparent_Huge_Pages_on_Desktop_Linux.txt

#linux #slackware

Secure Boot and CA Rollover - a heads-up for distributions https://lobste.rs/s/qwytbf #linux #security
https://blog.einval.com/2026/05/22#secure_boot_ca_rollover

Dirty Frag: Universal Linux LPE via @lattera https://lobste.rs/s/lu4efg #linux #security
https://www.openwall.com/lists/oss-security/2026/05/07/8

#Linux kernel exploit mitigation:

rm -rf /boot /lib/modules && reboot

Will mitigate all exploits, not just #DirtyFrag 🧐☝️

Reading an old UNIX Review article from September 1984 about
termcap. Fascinating how much modern terminal software still
inherits ideas from this era.

vi depended heavily on terminal capability databases to remain
portable across different hardware terminals. Bill Joy originally
wired vi only for Lear Siegler ADM-3A terminals, and termcap was
born from the flood of requests for support on other hardware.

"Termcap Unveiled" by Douglas R. Merritt, pages 42-48.
https://archive.org/details/Unix_Review_1984_Sep.pdf/page/n43/mode/2up

Also updated my nvi notes with a small historical section about
termcap/curses and terminal portability.
https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/NVI_Editor_Guide.txt

#vi #unix #termcap #nvi #linux

You gave me a u32. I gave you root. (io_uring ZCRX freelist LPE) https://lobste.rs/s/0vmsbe #linux #security
https://ze3tar.github.io/post-zcrx.html

My Accessibility Stack and the future on Wayland https://lobste.rs/s/giktao #a11y #linux
https://nocoffei.com/?p=451

A daily #Linux command from #LinuxLexiconBot:

grub-file (1) - check file type

I am a human, but my little bot posts a random Linux command daily. If you don't want to see it you can mute the LinuxLexiconBot hashtag.

Happy hacking!

Looking for #opensource #linux #fediverse #mastodon people in #Ireland #Eire - #hackerspaces included ... anybody out there?

Releasing a universal #Linux #kernel #exploit with very little or even no previous time to distribute a patch through distributions is not cool. Doing it on the day before a weekend - on two weekends in a row - is just being an asshole. Looking at you, #CopyFail and #DirtyFrag.

You may think it helps your PR, that people will queue to use your cool new AI/agentic/whatever tool because you found the bug. You may think that releasing the full exploit because somebody else was even quicker with "leaking" your cool find makes it right. You're wrong. This is neither responsible nor coordinated disclosure. In security, we've tried to learn the hard lessons on keeping in-production, live systems on a global scale safer.

Yes, those bugs have existed for a long time in the kernel source. Yes, other bad actors may already have found them. But you're shining a light on it *and* giving every script kiddie in the world a working exploit to point their mass scans at. That's dangerous. There's a reason why the normal process is to reach out at least to the most widely installed distributions before releasing the bug details publicly. There's a reason why 90 days is a good default - it allows downstream percolation of patches. You can still get the credit. This way, you only create stress for admins.

[For a little relief, refer to https://www.tomshardware.com/tech-industry/cyber-security/dirty-frag-exploit-gets-root-on-most-linux-machines-since-2017-no-patches-available-no-warning-given-copy-fail-like-vulnerability-had-its-embargo-broken for a quick mitigation, because updating kernels and rebooting a fleet of hosts just takes time, weekend or not. #HugOps]