｢ Arch Linux Project has confirmed that recent outages affecting its infrastructure are the result of an ongoing DoS attack. The disruptions have primarily hit the project’s main website, the Arch User Repository (AUR), and its community forums ｣
https://linuxiac.com/arch-linux-confirms-ongoing-denial-of-service-attack/
CachyOS August 2025 released, with a new packages website, LTS kernel as a fallback option, Niri WM window manager, new features in Proton-CachyOS, bootable btrfs snapshots in GRUB when choosing btrfs, and more
https://cachyos.org/blog/2508-august-release/
#cachyos #archlinux #linux #linuxlts #linuxdesktop #opensource #freesoftware
CachyOS August 2025 released, with a new packages website, LTS kernel as a fallback option, Niri WM window manager, new features in Proton-CachyOS, bootable btrfs snapshots in GRUB when choosing btrfs, and more
https://cachyos.org/blog/2508-august-release/
#cachyos #archlinux #linux #linuxlts #linuxdesktop #opensource #freesoftware
Every time there's a new version of #CopyQ I update it in hopes that it will have started working again now. And the answer is always no. It starts, but does not pick up anything I copy. It's been like this for a long time, across distros. I suspect it's got something to do with #Wayland? But I see Wayland mentioned in the changelog as if it works? Makes me sad, CopyQ is such an incredible tool. Is there anything similarly powerful for #Gnome? #Linux #LinuxApps
@forteller@tutoteket.no Fwiw, #CopyQ works fine for me in #ArchLinux #Plasma #Wayland... so it's hard to believe the problem is just it being incompatible with Wayland per se.
Avec la fin du support de Windows 10 par Microsoft, j'ai décidé de passer sous #Linux (#ArchLinux), bah c'est beaucoup plus facile que je pensais, si vous voulez faire pareil (si c'est pas deja fait) et que vous hesitez, dites vous que vous avez réussi à comprendre Mastodon 
Avec la fin du support de Windows 10 par Microsoft, j'ai décidé de passer sous #Linux (#ArchLinux), bah c'est beaucoup plus facile que je pensais, si vous voulez faire pareil (si c'est pas deja fait) et que vous hesitez, dites vous que vous avez réussi à comprendre Mastodon
Some how I am very envious of the 60MB RAM footprint while booting into a #linode #vps. The best I could get onto my #homelab is 300MB usage on a #Ubuntu cloud image. This is unfortunately the same as my desktop #ArchLinux with #KDE running.
The Ubuntu server image idled at 600MB RAM usage with #docker & #sshd. The culprits using most ram are #snapd & #multipathd.
Some how I am very envious of the 60MB RAM footprint while booting into a #linode #vps. The best I could get onto my #homelab is 300MB usage on a #Ubuntu cloud image. This is unfortunately the same as my desktop #ArchLinux with #KDE running.
The Ubuntu server image idled at 600MB RAM usage with #docker & #sshd. The culprits using most ram are #snapd & #multipathd.
I have been using Arch Linux + Hyprland full time for the last two weeks. No way back, I am really happy!
With https://omarchy.org/ you can get a fully functional and preconfigured system in a few minutes.
#omarchy #archlinux #Hyprland
Han colat programari maliciós al repo AUR de Arch Linux. Atents⚠️ ⚠️
Han colat programari maliciós al repo AUR de Arch Linux. Atents⚠️ ⚠️
ATENCIÓN usuarios de Arch, encontraron malware en los siguientes paquetes de AUR:
- librewolf-fix-bin
- firefox-patch-bin
- zen-browser-patched-bin
Si los instalaste se recomienda desinstalarlos cuanto antes. Un buen recordatorio de que hay que llevar cuidado con lo que instalamos desde AUR.
[aur-general] - [SECURITY] firefox-patch-bin, librewolf-fix-bin and zen-browser-patched-bin AUR packages contained malware
[aur-general] - [SECURITY] firefox-patch-bin, librewolf-fix-bin and zen-browser-patched-bin AUR packages contained malware
I woke up to a comment so smug, so perfectly soaked in gatekeeping and faux-righteous posturing, it earned its own blog post.
You want freedom? You want GNU/Linux to mean something?
Then maybe start by not telling disabled users to go fuck themselves with a smile.
This commenter thought they were defending "software freedom." What they were really doing was kicking people out of the room. Dismissing accessibility. Mocking effort. Pretending that cruelty is some kind of rite of passage. They quoted Stallman like it was scripture, ignored real-world experience like it was noise, and wrapped it all in condescension dressed as virtue.
I’ve spent over a decade in this ecosystem. Writing patches. Rebuilding broken stacks. Helping blind users boot systems upstream doesn’t even test. I didn’t "just install Arch and whine about the terminal." I lived in it. I survived it. I held it together when maintainers disappeared and no one else gave a damn.
But apparently, because I didn’t call it GNU/Linux™ and because I dared to talk about how this OS chews people up and spits them out, I’m lazy. I’m weak. I should "get a dog."
So I wrote a response. Line by line. No mercy. No euphemisms.
This isn’t just about one comment. This is about every time someone’s been told they don’t belong because they couldn’t learn fast enough, code well enough, or survive long enough. It’s about everyone who was pushed out while the gatekeepers patted themselves on the back for "preserving the spirit of free software."
You want a free system? Start by making it livable. Because freedom that demands you crawl bleeding through a broken bootloader isn’t freedom. It’s abandonment dressed in ideology.
And if this kind of gatekeeping is your idea of community?
You can keep it.
https://fireborn.mataroa.blog/blog/you-dont-own-the-word-freedom-a-full-burn-response-to-the-gnulinux-comment-that-tried-to-gatekeep-me-off-my-own-machine/
#Linux#GNU #FOSS#Accessibility#BlindTech#FreeSoftware#Gatekeeping#DisabilityInTech#OpenSource#Orca #ScreenReaders#ArchLinux#BurnItDown #blogpost
A space for Bonfire maintainers and contributors to communicate
