Slackware-current has now updated its testing XLibre packages to XLibre X Server 25.2.3, together with the latest XLibre driver snapshots.
I am already running this update on my ThinkPad T14 Gen 2i with Intel Tiger Lake graphics, and everything is working normally so far.
Slackware ChangeLog: git.slackware.nl/current/dif…
Slackware-minimal - A script and a set of packages for a minimal install of Slackware Linux server.
github.com/sagredo-dev/Slack…
逆襲のSlackware retweeted
It's here. Raven is now Open source!
A new Windows compatibility layer for Linux (and soon Mac OS). The website and code are now public alongside the whole story of the project, you can read about it here: useraven.org/news/introducin…
Waiting for your feedback, and please, be kind with it, it's young 🥹
#Linux #Windows #MaxOS #OpenSource #Development
逆襲のSlackware retweeted
Raven runs Windows apps on Linux, but not the Wine way 👀
While Wine translates Windows into Linux, Raven gives apps a Windows they recognize: real MSI installs, WinSxS, .NET 2.0 to 4.8, DirectX redists, and a snapshot before every install so nothing breaks your prefix.
Google Chrome, Steam (with the Unturned game installed and testes), Notepad++ and KeePass already works out of the box 🤟
I promise (because I already got at that point) better performance and out of the box experience. No hacking around with winetricks and similar tools.
#Windows #Linux #OpenSource
逆襲のSlackware retweeted
Happy 30th Birthday, KDE! lxer.com/module/newswire/ext…
Slackware + Btrfs subvolumes.
I wrote a short guide for installing Slackware64-current with @ and @home using the standard installer.
github.com/r1w1s1/code-notes…
逆襲のSlackware retweeted
Si eres programador en 2026, NO leas únicamente libros sobre:
- Lenguajes
- Frameworks
- Patrones
- Algoritmos
- Clean Code
La IA está cambiando qué habilidades hacen valioso a un programador.
Estos son los 10 libros que leería AHORA:
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 three physical machines + a VirtualBox VM I use professionally every day. It has been remarkably reliable.
Following ChangeLog.txt is part of running -current.
Interesting discussion on Reddit:
reddit.com/r/linux/comments/…
逆襲のSlackware retweeted
California’s Age Attestation Bill to Exclude Linux and All Open Source OSes lxer.com/module/newswire/ext…
逆襲のSlackware retweeted
Linux Kernel 7.0 Reaches End of Life, It’s Time to Upgrade to Linux Kernel 7.1 lxer.com/module/newswire/ext…
逆襲のSlackware retweeted
> AWSよりLinux、LinuxよりOSとは何か、みたいなことだ。
ほんまそれ
30代を捧げてきた技術が死にそう anond.hatelabo.jp/2025052822…
逆襲のSlackware retweeted
A single mismanaged repository can block security updates across your entire system.
In Linux-based production environments, even a single third-party repository with inconsistent dependency management can cause `dnf update` to fail. The impact, however, extends far beyond that specific package.
Because package managers evaluate dependency resolution as a single transaction, one unresolved dependency can block the entire update process — including critical OS-level security updates.
More critically, it disrupts the ability to apply security updates in a timely and controlled manner — a foundational requirement in any secure operating environment.
This issue often arises when repositories are treated as mutable distributions rather than controlled, versioned artifacts.
As a result, it leads to:
- Delayed application of security patches
- Increased exposure to known vulnerabilities
- Erosion of confidence in system maintainability and operational predictability
It also undermines reproducibility, making it difficult to reliably rebuild or recover environments over time.
From an operational and governance perspective, this introduces a systemic operational and security risk.
A poorly managed repository does not just affect its own software — it can effectively impact the security posture of the entire system.
By design, if a repository provides software that is responsible for system stability and availability, the consequences should be even more significant.
This is why repository governance should be treated as part of overall security and risk management, not merely as a packaging concern.
In practice, mature environments implement controls such as:
- Isolating or prioritizing repositories
- Mirroring and validating packages internally
- Establishing controlled update pipelines and staging environments
Repository reliability is not just a technical detail —
it is a reflection of operational discipline and software lifecycle maturity.
How is your organization ensuring that third-party repositories cannot compromise your update and security posture?
逆襲のSlackware retweeted
「FreeBSD」と「Slackware」--硬派な上級者向けOSの決定的な違い japan.zdnet.com/article/3524…
逆襲のSlackware retweeted
いきなりアンケート!!!
今環境でのLinuxの覇権は?
53%Debian系が神でしょ
15%Arch系最高!!
24%Slackware系がいいですよ
9%Linuxとか自分でビルドしてるわ
34 votes • Final results 逆襲のSlackware retweeted
Wine 10.9 Released With EGL Support For All Graphics Drivers
phoronix.com/news/Wine-10.9-…
逆襲のSlackware retweeted
現代のWebサイトは、すべてのクリック、ログイン、チェックアウトがスムーズに実行されるよう、継続的な監視を必要とします。そこで活躍するのが合成監視で、疲れ知らずの仮想訪問者のように動作し、実際のユーザに影響を与える前にパフォーマンスの問題を発見します。
speeddata.jp/blog/blog-2025-…
逆襲のSlackware retweeted
インターネットを活用したアプリケーションの提供が進化したことで、ユーザの体験に影響を与える要因をIT部門が把握しにくくなってきています。可視性が本来どうあるべきかを理解する良い方法は、「ファーストマイル」と「ラストマイル」監視という視点から考えることです。
speeddata.jp/blog/blog-2025-…





















