If you have 0B’s total enabled, not to be confused with used, then I’d recommend either enabling zswap or zram. zram compresses only ram and zswap compresses ram and then moves it to the drive as needed. Enabling one will improve your experience in general as currently your system just will try to shove everything in ram until it is full and need hard reset.

See [https://wiki.archlinux.org/title/Swap#Swap_file](Arch Wiki Swap) and [https://wiki.archlinux.org/title/Zswap](Arch Wiki zSwap)

It will still be faster than hitting the drives, whether that is a hard drive or nvme ssd. The compression code is highly optimized.

What “background services” breaks down to is things like the desktop. In the system monitor you can see a breakdown of what that is if you click on “show details sidebar” in top right. On my system for instance, plasmashell and kwin combined(the interface) is taking 700mb. Without the info from the sidebar it is harder to give advice.

Baloo is used for searching you system for files including contents. You can disable it if it isn’t something you’d use, limit it to certain directories or limit it to file names only. It will be under search in settings.

Edit: Also check how much swap you have enabled in the system monitor overview. You might look into turning on zram support if it isn’t already enabled which will compress ram as needed which might improve your experience.

The drives should work fine, for standard blurays and self wrote disks. There are a mature cli utilities and often the gui version is just a frontend for the cli tools. It is just an optical drive otherwise.

Arch Linux Wiki : https://wiki.archlinux.org/title/Blu-ray

Check out makemkv, which has a cli option, and their forum for compatibility for 4K blurays. Newer bluray drives have additional protection for 4K if I understood correctly.

I suspect part of it is modern web browsers and everything being online. That and “web apps” and such that take up WAY to much resources for what they do. In the name of security and justifiably so, each tab typically has it’s own thread/task which means more memory. They will free up as needed, but don’t do well always. With so many people just keeping tabs open rather than bookmarking them, users have also changed how they use their computers. So 16GB being a minimum and 32GB being recommended seems reasonable for a NEW computer. Remember, software is just going to need more resources in the future.

Existing computers will be fine for a while longer, but will get to that “compromised” state eventually.

Yeah and you’d think GNU would like the recognition too.

I’d rather have a little demon than a simp

Couldn’t they just call it IMP(Image Manipulation Program)?

I have heard it used that way in the last decade I think

There really isn’t any strong reason for them to do so. They already outsource manufacturing which is very flexible to needs. Apple does the same. Every PC company is using windows or linux as those are available to pretty much everyone. Patents? cheaper to just buy those. I am not seeing the hypothetical benefit.

The feature you are going to want to look for is USB Attached SCSI (UAS) or USB Attached SCSI Protocol (UASP) support.

Try opening a new terminal. If the commands don’t work, type “export PATH=/usr/bin” not quotes and try again and fix what you did.

I must have been tired when I did that math. I’d be happy with the year as well. Just don’t use the firefox/chrome model.

If semantic versioning is:

MAJOR version when you make incompatible API changes MINOR version when you add functionality in a backward compatible manner PATCH version when you make backward compatible bug fixes

then I think that would be on like 3.77.0 or something right now. Not terrible, but honestly prefer it to be like the major upped in the new year every year. It is about 43 years old,so 43.x in 2026. Would be easier to know how old a kernel release is without looking it up.

dead.letter is email draft in some clients when they crash.

Honestly I think it is because of DLSS. If you can get a $300 card that could do 4k DLSS performance well, why would you need to buy a xx70(ti) or xx80 card?

Yeah, bu can definitely be fun to mess around with. Linux Mesa supports the 40 series. I wonder how one would do in a BE-PowerPC system of around the same era?

I am not optimistic on it, but considering the Index’s(kit and controllers) are sold out, it wouldn’t surprise me that they might release a 2nd gen and announce HL3 along it.

I wonder why colorizing manpages like this is not default in most distros. That seems like an obvious thing to configure for end user’s quality of life.

My best guess would be that each terminal could display differently or be buggy and a “lowest common denominator” approach where it work everywhere. I know blue tends to be to dark unless I change the color to a lighter shade and the font could make a difference as well.

No

I wasn’t intending to come off confrontational, I apologize for that. I was looking at this from it sounding like you wanted any command on a system. I did find that you can colorize man. see script below for an example. As for busybox, it is a small project, so colorizing just it would be relatively easy and easy to add as a patch to a system. Not sure if that would upstream though as it is intended to work well on low memory systems among others.

#!/bin/bash

export PAGER="less -r"
export GROFF_NO_SGR=1
export LESS_TERMCAP_mb=$'\E[01;31m'
export LESS_TERMCAP_md=$'\E[01;31m'
export LESS_TERMCAP_me=$'\E[0m'
export LESS_TERMCAP_se=$'\E[0m'
export LESS_TERMCAP_so=$'\E[01;44;33m'
export LESS_TERMCAP_ue=$'\E[0m'
export LESS_TERMCAP_us=$'\E[01;32m'

man ls

Edit: it does seem that this man colorization is disabled by default.

Edit2: “export MANROFFOPT=-c” can replace “export GROFF_NO_SGR=1” to limit just man.

Edit3: source Arch Linux bbs