The kernel does stuff like

• process and CPU task management
• hardware abstraction
• memory management (at the process level),
• file system managment
• and resource isolation (such as randomized memory addresses (ASLR))

The rest of the OS provides the actual software that users interact with, like

• file managers
• desktop rendering and window management
• settings menus
• sound mixing between applications
• graphics rendering

How are you holding up?

Because I am a potato

You called?

It’s not a permanent one and it works for the time being, can’t see the reason for the downvotes honestly.

It’s just a bad idea in general. A better option would be to patch the binary to use 15. They both have the issue of forcing paru to work with a library it wasn’t explicitly designed for, but symlinking (or copying) 15 to 14 forces the hack to be “system wide” instead of restricted to a single binary

as well, your solution is “temporary” only if you remember to fix it, vs patching which is (by default) overwritten the next time paru is updated

it “works”, but it’s not something i’d recommend someone else do

You can either patch the binary

sudo patchelf --replace-needed libalpm.so.14 libalpm.so.15 "$(which paru)"

Or install paru-git

sudo pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru-git.git
cd paru-git
makepkg -si

Or do both, patch the binary, then use it to install paru-git (which is what i did)

I love arch, but I’m also a pedantic computer nut

It’s not for everyone

If you use any kind of ad blocker, switch to FireFox

Chrome is deliberately crippling ad block extensions via manifest v3

For a while, I had to do this after every kernel update

Turns out, i accidentally had two /boot folders. One was is own partition, and the other was on the rootfs partition. When Arch booted, the separate partition was mounted over the rootfs /boot dir, “shadowing” it

Except, UEFI / GRUB was still pointing to the rootfs partition. So when pacman installed a kernel update, it wasn’t able to update the kernel that UEFI was booting, but it was able to update the kernel modules

Kernel no likey when kernel modules are newer than the kernel itself

Idiocracy

I enabled testing repos for KDE 6.0 early access, and they include an overlay like this that says it’s a test release

Despite thinking that was a good idea, it felt a little like this, lol

I would use it, if KDE plasma would support it in their settings GUI

Arch621

I feel like the people who complain about systemd have never tried to mess with sysVinit scripts before

6+ years ago, I was trying to configure a touchscreen HAT for a raspberry pi, and dicking with the init.rc script was a massive pain