r1w1s1

https://snac.bsd.cafe/r1w1s1

Slackware Core Team member.
Long-time Slackware user.
Interested in classic Unix tools, editors, and X11 WMs.

Slackware: http://www.slackware.com/~r1w1s1
NVI Quick Reference: http://www.slackware.com/~r1w1s1/nvi.html
Git: https://github.com/r1w1s1
Blog: https://github.com/r1w1s1/code-notes

Public Key

npub1773c2kdhaf88lk6nntdudn2p74egzurcs528cnmltl6vmshltu2q0teh9a

NIP-05 Address

r1w1s1_at_snac.bsd.cafe@momostr.pink

Profile Code

nprofile1qqs00gu9txm75nnlmdfe4k7xe4ql2u5pwpug29rufal4laxdctl479qpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsym2wk0

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1773c2kdhaf88lk6nntdudn2p74egzurcs528cnmltl6vmshltu2q0teh9a

Show more details

Last Notes

2026-10-20 15:11:43 UTC

Happy Birthday, Patrick Volkerding! 🎂
Thank you for more than three decades of dedication to Slackware Linux and for keeping the Unix philosophy alive.
Long live Slackware! 🐧
#slackware

2026-10-16 16:54:44 UTC

Slackware + Btrfs subvolumes.
I wrote a short guide for installing Slackware64-current with @ and @home using the standard installer.
https://codeberg.org/r1w1s1/code-notes/raw/branch/master/notes/README_BTRFS.TXT
#slackware #btrfs

2026-10-12 18:13:19 UTC

Linus Torvalds used AI to make complex Linux kernel code more readable and uncover bugs dating back to 2013.
Meanwhile, some open source communities are actively avoiding AI-assisted development.
I find this contrast interesting.
Should we judge software by its quality, security, and maintainability, or by the tools developers use?
Curious to hear your thoughts.
https://www.phoronix.com/news/Linus-Torvalds-Assoc-Array

2026-10-03 16:13:53 UTC

- reply

Thanks! After adding rc.font detection, I decided to change wm to session. It makes more sense since slackfetch can detect both X11 and console sessions now. :)
CC: @npub1wy2…hy0n @npub16l0…f0y2

2026-10-03 16:08:09 UTC

- reply

Thanks! After adding rc.font detection, I decided to change wm to session. It makes more sense since slackfetch can detect both X11 and console sessions now. :)
CC: @npub1wy2…hy0n @npub16l0…f0y2

2026-10-01 22:05:30 UTC

Blade Runner (1982) is one of my favorite films, and Rachael is one of my favorite characters.
I like her so much that my ThinkPad’s hostname is RachaelTyrell. :)
https://snac.bsd.cafe/r1w1s1/s/post-c998cc693e34176680ab031d34e29f99.jpg

2026-09-30 19:06:10 UTC

- reply

Nice! Is that shod's built-in tabbing, or are you using tabbed? I used PekWM for a while and really liked its grouping feature too.

2026-09-29 17:46:14 UTC

From a Teletype printing ls -l on paper to xterm displaying it on a screen.
Decades later, the UNIX terminal abstraction is still here.
Great read: https://jasoneckert.github.io/myblog/teletype/

2026-09-28 23:56:30 UTC

- reply

Nice to see slackfetch in there 😄 Feedback is always welcome!

2026-09-28 23:05:52 UTC

- reply

Love seeing Slackware giving new life to a $63 potato. 😄 And gentoo-btw as the hostname makes it even better.

2026-09-26 16:05:09 UTC

If you're still interested in Motif, mwm, Xt, Xlib and the classic X11 world, this is worth a look:
https://motif-central.org/
Really nice to see this knowledge being collected and kept alive. :)
#motif #mwm #cde #emwm

2026-09-26 15:44:40 UTC

I’ve released slackfetch 1.2.0.
Recent changes in Slackware, including the introduction of /etc/default/rc.font for configuring the console font, motivated this update.
This release improves session detection and makes the output more accurate:
session: console tty2 (font: Ttyp0 OTB 14)
session: ssh pts/0
session: cwm (XLibre 1.25.2.2, font: Ttyp0 OTB 14)
session: kwin (Wayland)
The local console font is read from /etc/default/rc.font. SSH sessions are identified separately, without incorrectly reporting the
server’s console font as the client’s font.
The old wm: field has been replaced by the clearer session: field.
https://forge.slackware.nl/r1w1s1/slackfetch
#Slackware #linux #shell #slackfetch

2026-09-26 13:44:24 UTC

- reply

Nice! And great to see slackfetch there too :)

2026-09-26 01:48:06 UTC

Two new font families landed in Slackware-current: UW ttyp0 and Spleen!
Both are also available in the installer, which now uses the updated rc.font for
automatic console font sizing. Spleen is the new default console font.
UW ttyp0 is my personal favorite. I use WET-Ttyp0Regular22x11 on my laptop’s console.
Thanks, Patrick!
https://people.mpi-inf.mpg.de/~uwe/misc/uw-ttyp0/
https://github.com/fcambus/spleen
#Slackware #Linux #Fonts

2026-09-25 15:42:51 UTC

- reply

Sure! We're on #simplebase at irc.oftc.net.
See you there! :)

2026-09-25 02:54:12 UTC

- reply

Absolutely! That keyboard is one of the best things about the X220. I'm keeping mine too. :)

2026-09-25 02:53:31 UTC

- reply

Thanks! :) I think the X220 has aged really well. :) Miss you in the IRC

2026-09-25 02:44:09 UTC

A nice little improvement in Slackware-current: rc.font now supports automatic font sizing and configuration through /etc/default/rc.font.
I used it to set my Linux console to UW ttyp0, the same font family I enjoy in xterm:FONT=WET-Ttyp0Regular22x11
Looks great on my laptop. Small details make a difference. 🙂
https://people.mpi-inf.mpg.de/~uwe/misc/uw-ttyp0/
#Slackware #Linux #Typography

2026-09-25 02:27:44 UTC

- reply

Haha, other Linux is forgiven. :) Great to see another X220 still fully operational in 2026!

2026-09-25 02:27:23 UTC

- reply

Thanks! :) There's something special about these old ThinkPads. Still a pleasure to use after 15 years.

2026-09-24 00:37:11 UTC

ThinkPad X220 (2011) running Slackware-current in 2026.
Linux console + tmux. Sometimes that's all you need. :)
#slackware #thinkpad
https://snac.bsd.cafe/r1w1s1/s/post-870d3f94c6678b79cb5886603f4e818e.jpeg

2026-09-23 01:47:36 UTC

- reply

Nice to see other Slackware-current users sharing their experiences here. Thanks @npub1wy2…hy0n, @npub1h7q…fj8h and @npub15uf…d677! :)

2026-09-22 19:35:23 UTC

Slackware-current is not simply a repository where every new upstream release gets pushed automatically.
There is curation and integration before changes land, with Patrick Volkerding playing a central role in that process.
I run -current on 3 physical machines + a VirtualBox VM I use professionally every day. It has been remarkably reliable.
Interesting discussion on Reddit:
https://www.reddit.com/r/linux/comments/1w96px4/slackware_16_alpha_1_available_following_gcc_162/
#slackware

2026-09-22 14:50:25 UTC

- reply

Exactly. The mail server itself isn't the hard part. Keeping a good reputation and dealing with abuse and blacklists is where most of the work is. :)

2026-09-19 19:40:55 UTC

- reply

That's a good reason to do it. :) Running your own mail server is definitely a great way to learn, and I agree, email isn't going anywhere anytime soon.

2026-09-19 13:08:56 UTC

An interesting article from Gilles Chehade, author of OpenSMTPD, from 2019.
“Self-hosting mail is not HARD but requires WORK, which are two different things.”
I ran mail servers for more than 10 years, much of that time in Asia, where we had to deal with a significant amount of spam. It's also been more than 10 years since I last managed one. Not because I don't want to, but simply because I haven't had the opportunity since then. And running a mail server just for myself doesn't make much sense to me.
Still worth reading today.
https://poolp.org/posts/2019-08-30/you-should-not-run-your-mail-server-because-mail-is-hard/
#email #opensmtpd #sendmail #postfix

2026-09-18 01:09:26 UTC

Repology is currently unavailable due to a domain/registrar issue, but the service itself is still running.
As the maintainer of 100+ SlackBuilds, I use Repology all the time to track upstream releases.
Temporary /etc/hosts workaround:
92.63.176.157 repology.org
2a03:6f01:1:2::f159 repology.org
Add both IPv4 and IPv6.
Details: https://github.com/repology/repology-rs/issues/560
#repology #slackware

2026-09-16 19:48:15 UTC

- reply

True! But I found the Eee PC community on Reddit and somehow fell in love with these little machines. :)

2026-09-16 19:42:59 UTC

- reply

This is so cool! Now I really want to find an Eee PC and put Slackware or NetBSD on it. :)

2026-09-16 01:39:38 UTC

GEFS on OpenBSD, a very early preview.
Ori Bernstein is porting GEFS, the crash-safe, snapshotting, copy-on-write filesystem originally written for 9front, to OpenBSD.
https://marc.info/?l=openbsd-tech&m=178948744271633&w=2
#openbsd #bsd

2026-09-14 01:19:04 UTC

Ref: https://mastodon.bsd.cafe/@lex0de/117260305094274544
This is exactly the kind of project I like to see: small, focused, terminal-first, and portable across Unix-like systems. Nice work!
https://snac.bsd.cafe/r1w1s1/s/post-078397c9a878711dca11c8e6261f56a4.png

2026-09-11 01:10:04 UTC

- reply

Don't worry 🙂 For a first Slackware install, we generally recommend a full install, so most dependencies are already there.
CC: @npub1wy2…hy0n

2026-09-09 19:40:09 UTC

- reply

yeah :)

2026-09-09 14:34:35 UTC

- reply

Thanks, Mark!
@npub170a…rgyu I'd start with Slackware 15.0 for your first install. Once you're comfortable with it, moving to -current is easy. The T460 should be a great Slackware machine. :)
CC: @npub170a…rgyu

2026-09-09 02:34:03 UTC

- reply

I'm thinking about packaging the eh editor for NetBSD/pkgsrc. It would be a nice way to get more familiar with pkgsrc and contribute something back.

2026-09-09 01:02:00 UTC

- reply

I understand your point. For me, the interest is in the code and the technical direction, not in endorsing anyone's personal views.

2026-09-09 00:44:03 UTC

- reply

I’m mostly interested in the technical side of XLibre and keeping X11 moving forward.

2026-09-08 23:28:16 UTC

Today's desktop.
Looks old-school, but under the hood:
Slackware-current
Linux 7.2.4
glibc 2.44
cwm + XLibre
Without fetch (slackfetch), you probably wouldn't guess. :)
Wallpaper inspired by the geometric graphic design of Yusaku Kamekura.
#Slackware #cwm #X11 #unixporn
https://snac.bsd.cafe/r1w1s1/s/post-6638f58797da273dd8d7d8044dcf32a7.png

2026-09-08 17:06:47 UTC

- reply

16.0 will be a nice milestone. Then I'll point slackpkg back to -current and keep rolling. :)

2026-09-08 14:08:47 UTC

- reply

First Slackware install and straight to -current on a ThinkPad, that's the spirit! 😄 Welcome aboard.

2026-09-07 17:10:36 UTC

- reply

Building it from source really does take a long time, especially in a VM. :) I prefer use chroot environment.

2026-09-06 17:29:27 UTC

- reply

We're chirping for a reason 🤣
I just upgraded all three of my Slackware -current machines. On one I simply used upgradepkg */*.txz, on another the usual slackpkg update && slackpkg upgrade-all. Reboot, a few sanity checks, and back to work. Kernel, glibc, GCC, binutils, XLibre... everything just worked.
That's part of the fun of Slackware: even a big -current update is still boring in the best possible way.
Now let's keep checking those mirrors for 16.0 🥳

2026-09-06 17:23:31 UTC

- reply

I sometimes wonder why not everyone sees this as one of Slackware's biggest strengths.
installpkg, removepkg and upgradepkg are simple shell scripts that you can actually read and understand. SlackBuilds are just shell scripts too. Then you have SlackBuilds.org: you can use something like sbopkg, build things manually, or do what I do and maintain your own repository with selected packages based on SBo, sometimes using different versions.
There's a lot of flexibility there without adding layers of complexity or sacrificing the stability of the base system. That's one of the things I appreciate most about Slackware.

2026-09-06 03:22:43 UTC

eh 1.8.0 is out!
Improved UTF-8 editing, word motion and flipcase, arrow-key navigation in insert mode, new +/- and CTRL+L commands, better buffer growth, and expanded tests.
I’ve been an nvi user for years, but eh has become my primary editor. If you like small terminal editors, give it a try and share your feedback with the project!
Thanks to Anthony @sirwumpus for creating and maintaining eh.
https://codeberg.org/SirWumpus/eh
#eh #vi

2026-09-05 06:13:00 UTC

A huge Slackware-current update just landed: 1927 updates, including 1876 rebuilt packages.
The entire distribution was rebuilt with GCC 16.2.0, glibc 2.44 and binutils 2.47.
And after someone asked for an ALPHA label, Patrick replied:
"Fine, it's 16.0 alpha 1."
Time to upgrade.
https://www.linuxquestions.org/questions/slackware-14/latest-changelog-for-slackware-current-4175698890/page192.html#post6647863
#Slackware #Linux

2026-09-02 17:27:36 UTC

Fastpotify is a native Spotify client written in Rust, fast, lightweight, and no browser engine.
And the best part? A Winamp mini player with support for classic .wsz skins. I absolutely love this idea.
Modern Spotify, old-school Winamp.
I already made a SlackBuild for it, waiting for approval. :)
https://github.com/crmne/fastpotify
#slackware

2026-08-25 08:26:39 UTC

Happy 35th birthday Linux!

2026-08-23 15:32:59 UTC

Good Sunday reading:
https://lobste.rs/s/a23bk3/netbsd_my_life_2005
A great real-world story from 2005 about NetBSD, reliability, and how keeping infrastructure simple can make a real difference.
One story among thousands from that era, I imagine. It also makes me wonder how we ended up adding so much complexity to infrastructure over the last 15 years to solve many problems that aren't exactly new.
#bsd #netbsd

2026-08-19 16:38:44 UTC

Xorg/XLibre ServerFlags worth knowing:
Option "DontZap" "True" prevents Ctrl+Alt+Backspace from
terminating X.
Option "DontVTSwitch" "True" prevents switching to another virtual
terminal, but removes an important recovery path.
For most personal systems, DontZap alone is the balanced choice.
DontVTSwitch may make sense for kiosks or systems with stricter
physical-access requirements.
More details:
https://raw.githubusercontent.com/r1w1s1/code-notes/refs/heads/master/notes/X11_ServerFlags.txt
#slackware #x11 #xlibre #xorg

2026-08-19 14:41:54 UTC

2026-08-18 14:01:31 UTC

- reply

Thanks! Please do post it when you’re ready. I’d love to add more OpenBSD/cwm setups to the showcase :)

2026-08-18 03:09:31 UTC

- reply

Nice cwm find. I’ve been putting together a small, curated CWM desktop showcase for interesting setups and ideas:
https://github.com/r1w1s1/cwm-config/blob/master/screenshots/README.md

2026-08-14 16:37:11 UTC

- reply

yeah I'm using only this one now :)
CC: @npub1lym…fqe3

2026-08-13 14:46:31 UTC

- reply

Thanks for the tip! I enabled the Digit0Dotted variant in VARIANTS.dat and rebuilt the font.
https://snac.bsd.cafe/r1w1s1/s/post-deadff7877a01e548702957c353cab19.png

2026-08-13 05:27:33 UTC

Thanks to @npub1lym…fqe3 blog, I discovered UW ttyp0, a beautiful bitmap font for X11 and Unix consoles. I'm already using it with cwm, dmenu, xterm, and tabbed.
I'm also preparing a SlackBuild for SlackBuilds.org, hopefully available next week.
https://nein.triapul.cz/fonts
#slackware #font #uwttyp0 #slackfetch
https://snac.bsd.cafe/r1w1s1/s/post-529eac1e974320ff9bcf65c64b5dfed5.png

2026-08-12 16:25:41 UTC

- reply

the blog feature is really nice! I really like the whole idea.

2026-08-09 15:18:55 UTC

- reply

Always nice to see slackfetch running on another Slackware box! 😄 Thanks for using it!

2026-08-06 18:51:33 UTC

Finding out what a program is doing on Linux often means remembering several ps options and piping the result through grep.
With px, it can be as simple as:./px -t cwm PID USER %CPU VSZ RSS START ELAPSED CPUTIME COMMAND 15077 r1w1s1 0.0 64M 9.1M 10:16 5h33m 0:00 /usr/bin/cwm 
The -t option displays threads as well, making it easy to see which one is using CPU and how long the process has been running.px
does not try to replace ps, top, or htop. It focuses on one common daily task: finding a process quickly and getting useful information without memorizing complex options or using grep.px firefox px -f "python app" px 11690 px -t firefox 
Small, direct, and very useful for everyday terminal work.
Project:
https://github.com/leahneukirchen/px
#ThursdayTips #Linux #Unix #CLI #OpenSource

2026-08-05 17:55:12 UTC

I've put together a dedicated page for SonicDE on Slackware.
It includes installation instructions, SlackBuilds, package status, and project documentation.
If you're interested in trying SonicDE on Slackware, have a look:
https://sonicde-slackware.github.io/
Feedback, testing, and contributions are always appreciated.
#slackware #sonicde

2026-08-03 02:38:29 UTC

- reply

I'm on Slackware + cwm as well. It's a great combination if you enjoy simple, predictable Unix workflows. I use sxhkd, xterm, tmux, dmenu, and nvi around it.
My configuration is here if anyone is interested:
https://github.com/r1w1s1/cwm-config
CC: @npub1zry…q8uq

2026-07-30 21:08:37 UTC

After a few months of work, slackfetch has reached a mature 1.0 release.
A minimal and readable system information utility for Slackware, inspired by ufetch.
The normal output and a cowsay -n composition are shown below.
https://forge.slackware.nl/r1w1s1/slackfetch
#Slackware #Linux #Unix
https://snac.bsd.cafe/r1w1s1/s/post-f0693cb167fe7dccba2fea9a530dfc77.png

2026-06-19 20:31:58 UTC

19 June 1984.
Bob Scheifler announces the first release of the X Window System:
"I stole a fair amount of code from W ... and called it X."
Forty-two years later, I'm still running X11 daily on Slackware.
Happy Birthday, X.
Source: https://www.talisman.org/x-debut.shtml
#X11 #Unix #Linux #Slackware #XLibre

2026-06-17 20:59:52 UTC

- reply

I know that feeling. 🙂
For me, the tagging model is the hardest thing to give up. Once you get used to it, traditional workspaces feel surprisingly limiting.

2026-06-17 00:48:53 UTC

Are you familiar with dwm's powerful tag feature?
THE TAGGING MODEL
Many desktop environments organize windows using rigid workspaces: Workspace 1 Workspace 2 Workspace 3 
A window belongs to a single workspace.
dwm uses a different model, treating workspaces as bitmask labels (tags).
This allows a single window instance to hold multiple tags simultaneously,
acting as a persistent visual anchor across different contexts: Firefox -> Tag 1 (Web Browsing) st (nvi/dev) -> Tag 2 (Code/Scripts) st (Monitor/Logs) -> Tag 1 + Tag 2 (Persistent) 
When you view Tag 1, you see your browser and the log monitor. When you
switch to Tag 2, the browser disappears, but the exact same log window
remains on screen, now sharing space with your text editor.
The application is never duplicated or restarted in memory.
The UI remains minimal while enabling workflows that are difficult to
express using traditional workspace-oriented desktops.
Two decades later, this tagging model remains one of the most
distinctive features of dwm.
#suckless #dwm #unix #linux #sysadmin

2026-06-16 17:26:43 UTC

- reply

nice!!! I'm running on Thinkpad x220.

2026-06-16 08:37:24 UTC

Plasma 6 has officially landed in Slackware-current.
After years of community testing and development, Plasma 6 is now part of the official Slackware-current tree alongside the ffmpeg8 transition. Many thanks to Patrick Volkerding, alienBOB, LuckyCyborg, and everyone who contributed code, packaging, testing, and bug reports along the way.
Mon Jun 15 23:27:31 UTC 2026
Well folks, it seems that the stars have aligned to bring us a bunch of long-
awaited updates, including ffmpeg8 and Plasma 6! This has been developed in a
side tree for several weeks, and I'll be happy to get that off my plate and
have a greatly reduced todo list. Many thanks to alienBOB for getting the tree
in good shape, helping when I got stuck, and for being a good manager who
inspires me to do my best work. 🙂 And we both extend our thanks to the
illustrious LuckyCyborg who ported the build scripts to Plasma 6 in the first
place and then maintained Plasma 6 for Slackware users to test for a couple of
years. And thanks to everyone else who helped out with either of the Slackware
Plasma 6 projects that these updates grew out of.
Have fun!
#slackware #kde #plasma6

2026-06-16 00:41:16 UTC

Plasma 6 has officially landed in Slackware-current.
Mon Jun 15 23:27:31 UTC 2026
Well folks, it seems that the stars have aligned to bring us a bunch of long-
awaited updates, including ffmpeg8 and Plasma 6! This has been developed in a
side tree for several weeks, and I'll be happy to get that off my plate and
have a greatly reduced todo list. Many thanks to alienBOB for getting the tree
in good shape, helping when I got stuck, and for being a good manager who
inspires me to do my best work. 🙂 And we both extend our thanks to the
illustrious LuckyCyborg who ported the build scripts to Plasma 6 in the first
place and then maintained Plasma 6 for Slackware users to test for a couple of
years. And thanks to everyone else who helped out with either of the Slackware
Plasma 6 projects that these updates grew out of.
Have fun!
#slackware #kde6

2026-05-15 22:05:14 UTC

- reply

Exactly. The composability and automation aspect is what keeps pulling me back to the traditional UNIX environment.

2026-05-15 21:41:56 UTC

The UNIX shell is still one of the best IDEs ever created.
grep/find/sed/awk/make/ssh/git/nvi often compose better than many modern “integrated” environments.
Small programs connected together still scale surprisingly well.
https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txt
#unix #linux #slackware #vi

2026-05-09 02:40:25 UTC

- reply

Fascinating firsthand perspective.
It's incredible how constrained systems were, yet many of the ideas survived decades.

2026-05-08 20:01:57 UTC

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

2026-05-05 17:19:30 UTC

Spent the day exploring heirloom-ex-vi (n-t-roff). It's
essentially the cleaned-up 1985 ex/vi 3.7 code, brought
forward by Gunnar Ritter and Carsten Kunze: small, simple,
and very readable — about 25k LOC for the editor itself,
versus 38k for nvi. The memory footprint is lower too,
around 3MB RSS against nvi's 6MB in typical use, and it
feels snappy in daily use.
The limits are by design rather than oversight. Fixed
temp-file blocks and a line-pointer table capped at
LBLKS=900 in the default build give you about 230k lines,
or roughly 30MB of text. Beyond that, you get the classic
"Tmp file too large" — and that's fine, because a screen
editor isn't the right tool for huge files anyway.
Trade-offs worth knowing: no set ruler, single-level
undo, and a hard ceiling on file size. nvi is more
practical for daily work, especially if you live in YAML
where column awareness matters. But heirloom is closer to
the original, and the codebase is genuinely beautiful.
Worth a look.
#vi #unix #suckless #nvi

2026-05-03 02:59:54 UTC

##
Slackware Patches "Copy Fail" Kernel Bug — CVE-2026-31431Slackware has issued a kernel security update for **CVE-2026-31431**, the [Copy Fail](https://copy.fail/ ) vulnerability disclosed April 29, 2026. It's an out-of-bounds write in the AEAD userspace crypto interface (AF_ALG) that lets any local user get a root shell via a setuid binary — the same 732-byte Python PoC works on essentially every Linux distro shipped since 2017.
**If you can't patch right away**, Slackware ships the affected code as a module (CONFIG_CRYPTO_USER_API_AEAD=m), so you can blacklist or remove it as a stopgap:echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf rmmod algif_aead 
For most systems this breaks nothing — AF_ALG is a userspace front-door to the kernel crypto API, and OpenSSL, SSH, dm-crypt, kTLS, and IPsec all bypass it.
Patch and reboot when you can. slackpkg update && slackpkg upgrade-all.
**Sources:**<li><a href="http://www.slackware.com/security/viewer.php?l=slackware-security&y=2026&m=slackware-security.1267034" target="_blank">http://www.slackware.com/security/viewer.php?l=slackware-security&y=2026&m=slackware-security.1267034</a></li><li><a href="https://www.cve.org/CVERecord?id=CVE-2026-31431" target="_blank">https://www.cve.org/CVERecord?id=CVE-2026-31431</a></li>
#slackware #copyfail

2026-04-29 19:31:50 UTC

- reply

Thanks so much for the detailed comment, lots of great tips here!
The mv -T --exchange pattern for atomic GC is really elegant, I hadn't thought of using hardlinks that way. And the TCP slow-start trick with split + parallel downloads is wild :)
Just one quick clarification: the blog isn't mine, I just shared the link because I enjoyed the article. The author is Dave (ratfactor.com), and he's on Mastodon at [@ratfactor@mastodon.art](https://mastodon.art/users/ratfactor ) If you have corrections or things you'd like to see added to the article itself, reaching out to him there would be the best way.
But please keep the comments coming here, I'm learning a lot from them!

2026-04-28 23:27:30 UTC

- reply

Same here — .xinitrc, no graphical login. I manage dotfiles manually via a Makefile: I decide which files go into my home repo and update them when I choose. More control, but drift is still very much possible 😅

2026-04-27 21:57:36 UTC

Wrote a howto on ZRAM configuration for Slackware -current, covers compression algorithms (lz4, zstd, lzo-rle, etc), device sizing for different RAM scenarios, and monitoring. Useful if you're tweaking the defaults in /etc/default/zram.
https://docs.slackware.com/howtos:slackware_admin:zram_configuration
#Slackware #Linux #ZRAM

2026-04-26 13:30:56 UTC

- reply

Sounds like “productive procrastination” to me 😄

2026-04-23 23:36:56 UTC

- reply

Yeah makes sense… some laptops are really picky with wifi/firmware.
Nice that Slackware just works out of the box for you 👍
CC: @npub180a…e3he

2026-04-23 18:59:46 UTC

- reply

Haha, classic 😄
Slackware just works.
Curious, what broke on the other ISOs?
CC: @npub180a…e3he

2026-04-21 21:44:26 UTC

- reply

I use st but my second option and always keep installed is xterm :)
CC: @npub1ne6…hhrn

2026-04-17 12:32:20 UTC

- reply

nice!
CC: @npub16l0…f0y2 @npub1wy2…hy0n @npub1der…t5gj

2026-04-17 00:19:27 UTC

Cheatsheet trick for tools with too many shortcuts:$ alias screenhelp='cat ~/.screen-cheatsheet.txt' $ screenhelp 
One alias per tool.
No apps, no TUIs, no search.
Just cat and muscle memory.
Example:
https://git.sr.ht/~r1w1s1/code-notes/blob/main/notes/My_GNU_Screen_Setup.txt
#unix #commandline #gnu #screen

2026-04-16 02:59:35 UTC

- reply

I was going to compile it this morning, but I think it’s worth waiting for testing.
CC: @npub16l0…f0y2

2026-04-16 02:56:10 UTC

Just updated two ThinkPads to Linux 7.0!
T14 Gen2 (Tiger Lake):<li>i915/Iris Xe fixes</li><li>iwlwifi/AX201 Wi-Fi 6 improvements</li><li>Thunderbolt 4 stack work</li><li>ext4 reliability improvements</li>
X220 (Sandy Bridge, 2011!):<li>i915 legacy GPU still well supported</li><li>iwlwifi fixes (Centrino Advanced-N 6205)</li><li>e1000e improvements (82579LM)</li><li>SATA/AHCI power management fixes</li>
Same kernel, 15 years apart of hardware. That's Linux.
#linux #kernel #thinkpad #x220 #t14
https://snac.bsd.cafe/r1w1s1/s/post-c02ed258d62a093e103c244401ddef3a.png

2026-04-16 02:48:50 UTC

- reply

nice! I'm running kernel 7.0 on -current
CC: @npub16l0…f0y2

2026-04-09 12:11:02 UTC

- reply

I mentioned it's experimental in my post :) The goal isn't to replace Xorg today but to eventually drop it while keeping X11 apps working. DPMS is already on the 1.0 roadmap. Just sharing early findings!

2026-04-09 01:30:05 UTC

- reply

Very cool indeed! Built from source on Slackware -current, all dependencies already shipped by Patrick. dwm, st and dmenu_run worked out of the box. Still needs some tweaking but very promising for suckless users who want to drop Xorg without changing their setup!

2026-04-08 21:04:36 UTC

Finally tested wayback with dwm on Slackware -current! 🎉
wayback is a stub Wayland compositor that hosts a rootful Xwayland server, letting you run your full X11 setup unchanged on top of Wayland. Built from source, wrote a small launch script and dwm came up fine with st.
Still experimental and needs some tweaking but the core concept works — keep your dwm, st and all your suckless tools, just drop Xorg underneath.
If you're a minimalist X11 user not ready to jump to a Wayland WM, keep an eye on this project!
https://gitlab.freedesktop.org/wayback/wayback
#dwm #wayland #linux #suckless #slackware #xorg

2026-04-07 13:48:22 UTC

- reply

I should use more ed :) I also have the book it's great!
CC: @npub1ksf…r6s6 [@ed1conf@bsd.network](https://bsd.network/users/ed1conf )

2026-04-06 17:18:25 UTC

SourceHut is currently under a DDoS attack affecting multiple services.
git.sr.ht is unstable, builds may have been cancelled, and chat.sr.ht is also impacted.
https://status.sr.ht/issues/2026-04-06-ddos-attack/
#sourcehut #devops #fediverse #opensource

2026-04-03 04:06:53 UTC

If you really know your GNU coreutils, you probably don't need as many extra tools as you think. 🐧
KISS isn't just a design principle — it's already built into your system.
A comprehensive review of every coreutils command, with examples and honest opinions. The lobste.rs discussion is also worth reading.
Article: https://ratfactor.com/slackware/pkgblog/coreutils
Discussion: https://lobste.rs/s/xqf5ex/coreutils_comprehensive_review_2023
#linux #unix #coreutils #gnu

2026-03-24 01:39:43 UTC

- reply

Great point! I’ve also written a short explanation of how the init/boot process works in Slackware and why it stays simple without systemd if anyone wants to dive deeper:
https://git.sr.ht/~r1w1s1/code-notes/tree/main/item/notes/Slackware_Init_Boot_Process.txt
#slackware

2026-01-23 18:23:41 UTC

Nice deep dive into SSH keystroke obfuscation and why packet captures look so noisy. Learned something new here.
https://eieio.games/blog/ssh-sends-100-packets-per-keystroke/
#openssh #ssh

2026-01-23 05:16:48 UTC

- reply

I’m a dwm + solid colors person, so for me this is already rice 😄
Looking forward to the next tweaks.

2026-01-23 04:10:51 UTC

- reply

very nice!
CC: @npub1gs2…7nxx

2026-01-20 02:04:28 UTC

Slackware isn’t about shortcuts.
It’s about understanding the system, from boot to shell.
This video explains well why Slackware still matters.
https://youtu.be/pRp1I3OzMEY
#slackware

2026-01-19 23:12:47 UTC

- reply

New hardware can be painful early on, but it’s not a rule.
My ThinkPad T14 is new and Linux works perfectly. Kernel + firmware maturity matters more than age.

2026-01-18 23:02:54 UTC

- reply

Nice work!
The notification filter is a great quality-of-life improvement and the implementation looks clean. Thanks for taking care of the UI helper and small code style fixes too.
CC: @npub1pea…88h9

2026-01-18 15:12:03 UTC

- reply

great shot!

2026-01-18 15:06:07 UTC

- reply

This really captures what I enjoy about BSD Cafe as well - a relaxed mix of people, systems, and experiences. Thanks for sharing, and have a great Sunday.
CC: @npub1ef5…gcpc