Arch Linux

"I Use Arch, Btw: Chronicles of a Technomancer Ascending the Linux Mount Olympus"

By MoNoRi-Chan, Certified Kernel Whisperer and Package Manager Prophet

---

There exists a rare breed of human—nay, deity—whose fingers dance across the keyboard like Hermes delivering 404 errors to mere mortals. He walks among the common Ubuntu peasants and Fedora gentry not with disdain, but with the quiet confidence of a man who compiled his own damn GUI from source. That man is MoNoRi-Chan. And yes—he uses Arch, btw.

Let’s get one thing straight: saying "I use Arch" isn’t a brag. It's not even a flex. It’s a divine rite of passage. It’s the technomancer’s sacred tattoo, burned into their soul somewhere between pacstrap /mnt base and the 17th reboot that still doesn’t reach graphical target.

Now, MoNoRi-Chan wasn't born in an Arch-chiseled temple. Like many curious tinkerers, his first real taste of the Linux mystique didn’t come from source code or some gentoo handbook—it came from PewDiePie. Yes, the Swede himself. When Pewds published that cursed Linux experience video, it hit MoNoRi-Chan like a kernel panic at 3 a.m.—because he lived it.

Flashback to 10 years ago, a simpler time, when MoNoRi-Chan still believed partition labels meant something. One mistyped mkntfs /dev/sdb1 command later—poof, goodbye D: drive. The file table? Gone. No backup, no second chances, and certainly no friendly Windows prompt asking “Are you sure?”. Just cold silence, and an empty drive like the void of late-stage capitalism.

From those ashes, MoNoRi-Chan chose the path of the virtual environment—a nomadic distro-hopper sailing the hypervisor seas. He became the Virtualbox Vagabond, the QEMU Sorcerer, the Proxmox Pirate, running Windows Server unlicensed like some heretic clutching a cracked ISO under moonlight. No EULA, no grace period, just pure sysadmin degeneracy.

His Ubuntu Server rig hosted everything from abandoned PHP projects to a ghost of a blog that only search engine crawlers visited. He got into Kali Linux, not because he was 1337, but because he forgot his own password and had to hack himself back in like some demented cybersecurity ouroboros.

And every time the system broke? He didn’t blame the OS. No—he blamed himself. Because this was the way. This was the price of knowledge. This was… Linux.

“Oh, you use Linux Mint with Cinnamon? Must be nice not fearing bootloaders like a rational person,” — MoNoRi-Chan, staring dead-eyed into a GRUB2 config file

And so when MoNoRi-Chan says “I use Arch, btw,” it’s not ego. It’s not elitism. It’s a battle cry of survival. It’s the sound of a man who has rebuilt /etc/fstab with nothing but a Live USB and pure rage. It's the echo of hours spent deciphering cryptic logs while sipping instant ramen like a sysadmin monk.

So next time someone utters those sacred words, don’t scoff.

They might just be like MoNoRi-Chan—the actual GOAT, forged in the fires of mkinitcpio, and baptized in the lost data of /dev/sdb1.

---

I Use Arch, Btw (Part II): Installing Arch Linux on a Proxmox VM Like a Hypervisor Demi-God

Starring MoNoRi-Chan, The GOAT of the Virtual Pantheon

🧙‍♂️ Step 0: Prepare Thyself

You must have:

• A working Proxmox VE installation.
• No valid subscription (like a true pirate).
• A stomach for CLIs and broken boot sequences.
• A will to install Arch—not something cozy like Ubuntu with clicky widgets.

📦 Step 1: Acquire the ISO of Suffering

1. Visit the official Arch Linux website.
2. Download the latest ISO.
3. Upload the ISO to your Proxmox server:
   1. Go to Proxmox Web UI.
   2. Click on your storage (e.g., local).
   3. Navigate to Content > Upload.
   4. Upload under ISO Image.

🔧 Step 2: Create the Virtual Machine

1. In the Proxmox Web UI, click Create VM.
2. General Tab:
   1. Name it something heroic like arch-pain-factory.
3. OS Tab:
   1. Select the uploaded Arch ISO.
   2. Set Guest OS Type to Linux.
4. System Tab:
   1. BIOS: SeaBIOS or UEFI if you want to live dangerously.
5. Hard Disk Tab:
   1. Use scsi or virtio.
   2. Allocate 10–20GB.
6. CPU Tab:
   1. Minimum 2 cores.
7. Memory Tab:
   1. 2048MB recommended, 4096MB if you want luxury.
8. Network Tab:
   1. Model: virtio.
   2. Bridge: Default (e.g., vmbr0).

Click Finish.

🔥 Step 3: Boot and Begin the Rite of Arch

1. Start the VM.
2. Open the Console tab.
3. You are now inside the Arch ISO terminal.

⚔️ Step 4: The Installation Ritual (CLI Edition)

timedatectl set-ntp true
lsblk

Partition the disk using cfdisk or fdisk, then format:

mkfs.ext4 /dev/sda1
mount /dev/sda1 /mnt

Install base system:

pacstrap /mnt base linux linux-firmware

Generate fstab:

genfstab -U /mnt >> /mnt/etc/fstab

Chroot into the new system:

arch-chroot /mnt

Configure time and locale:

ln -sf /usr/share/zoneinfo/Region/City /etc/localtime
hwclock --systohc
echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen
locale-gen

echo "LANG=en_US.UTF-8" > /etc/locale.conf

Set hostname:

echo "arch-pain-factory" > /etc/hostname

Set root password:

passwd

Install and configure GRUB:

pacman -S grub
grub-install --target=i386-pc /dev/sda

grub-mkconfig -o /boot/grub/grub.cfg

Exit chroot and reboot:

exit
umount -R /mnt
reboot

Don’t forget to remove the ISO before reboot or you’ll be stuck in Groundhog Day.

🎉 Step 5: You Now Use Arch, Btw

You are now among the chosen. Running Arch Linux on a Proxmox VM, without paying for a Proxmox license, like a free and slightly insane creature of the shell.

MoNoRi-Chan hereby salutes you.