<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on Muhammad Nuh</title><link>https://hexrogue.github.io/tags/linux/</link><description>Recent content in Linux on Muhammad Nuh</description><generator>Hugo</generator><language>en-us</language><managingEditor>ikanlemas0@gmail.com (Muhammad Nuh)</managingEditor><webMaster>ikanlemas0@gmail.com (Muhammad Nuh)</webMaster><lastBuildDate>Tue, 22 Aug 2023 00:00:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Arch Broke, and I Am Glad</title><link>https://hexrogue.github.io/blog/arch-broke-and-im-glad/</link><pubDate>Tue, 22 Aug 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/arch-broke-and-im-glad/</guid><description>&lt;p&gt;Yes, Arch is my daily driver. No, I will not shut up about it. But this is not a conversion post. This is about the Tuesday an update left me staring at a boot menu with no Arch in it, and why I am glad it happened. The boot menu is a polite way of saying the computer has decided to take a personal day.&lt;/p&gt;&#10;&lt;h2 id="the-update-that-removed-my-os-from-the-menu"&gt;The update that removed my OS (from the menu)&lt;/h2&gt;&#10;&lt;p&gt;Pacman did its thing, I rebooted, and the bootloader offered me exactly one option: the fallback that also did not work. My root partition was fine. My kernel was fine. The boot entry was just gone. Somewhere between the kernel package and my EFI partition, a path disagreed with another path.&lt;/p&gt;</description></item><item><title>Arch Linux Tips: Survive and Enjoy</title><link>https://hexrogue.github.io/blog/arch-tips-survive-and-enjoy/</link><pubDate>Wed, 14 Jun 2023 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/arch-tips-survive-and-enjoy/</guid><description>&lt;p&gt;Arch has a reputation for breaking. Mine breaks about twice a year, takes twenty minutes to fix, and teaches me something each time. The secret is not skill. It is habits, all of them boring, most of them learned while staring at a black screen and pretending the silence is a feature.&lt;/p&gt;&#10;&lt;h2 id="tip-one-read-before-you-press-y"&gt;Tip one: read before you press Y&lt;/h2&gt;&#10;&lt;p&gt;Pacman tells you exactly what it is about to do. Read it. Version jumps on kernels, drivers, and bootloaders deserve a glance at the Arch news feed first. Major changes get announced there with manual steps attached. Five minutes of reading prevents ninety percent of breakage. The updates can wait until after coffee.&lt;/p&gt;</description></item><item><title>How to Spy on Any Program (Legally)</title><link>https://hexrogue.github.io/blog/spy-on-any-program/</link><pubDate>Mon, 05 Dec 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/spy-on-any-program/</guid><description>&lt;p&gt;Every program lies about what it does. Not maliciously. It just never tells you the full story. The installer says &amp;ldquo;quick setup&amp;rdquo; while writing files in six directories. The app says &amp;ldquo;no account needed&amp;rdquo; while phoning three analytics servers. It is not a conspiracy. It is a filing cabinet with no labels and a lock you can pick with strace.&lt;/p&gt;&#10;&lt;p&gt;After years of CTFs, homelab mysteries, and malware curiosity, I built a method for interrogating any program until it confesses. Five layers, cheapest first. This is the post I wish existed when I started.&lt;/p&gt;</description></item></channel></rss>