My favorite so far:

$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list

Thread 1 "gdb" received signal SIGABRT, Aborted.

I once wrote bind_front() and move_only_function likes in C++17. This nearly drove me mad because you cannot refer to a overload set by a name.

On the otherhand, I can now decipher the template error mess that the (g++) C++ compiler spews out.

what the actual fuck. 🤮

$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list

Thread 1 "gdb" received signal SIGABRT, Aborted.

Yeah, try debug that.

Well I meant two weeks is the longest period i can leave the system without updating and have no problems. And i have yet to break it with 300 pkgs updating at once.

Arch maintenance: 0. Install it once. (The proper way)

1. Every 2 weeks minimum pacman -Syu
2. Every 3 months merge/update configs in /etc.

I don’t get what is with this so hard? Yes, configs can be undecipherable but 90% time the merge involves just deleting the .pacnew versions.

A kernel was released that changed how the hash value got computed for casefolded filenames. (used for better windows compatibility) That kernel then went into production. This unfortunately split some file-systems that supported this into two incompatible versions, breaking the kernel rule 1.

There might now exist file-systems were created/modified with this bug present that the old/fixed kernels can’t understand.

I was reluctant to take this project, knowing well I would end up deleting nearly all existing code I would have to touch, all while having just mediocre skill writing its successor, if it ever becomes one.

I can no longer escape from this project, nor do have I will to.

deleted by creator

deleted by creator

100% Nope: A episode from supernatural, where ghouls half way succeed to eat Sam. (I consider it as the most gruesome horror I have ever seen, and I don’t think I have the stomach to see it ever again. The blood draining is a … no.)

Yellow brick road on otherhand hits the weird places spot of SCP, which I can’t get enough. (not horror really, but still)

The point when the AI hallucinations become useful is the point where I raise my eye brows. This not one of those.

I do this exact same expression when I’m forced to gain knowledge of something potentially personally catastrophic…

Python is just a pile of dicts/hashtables under the hood. Even the basic int type is actually a dict of method names:

x = 1
print(dir(x))
['__abs__', '__add__', '__and__', '__bool__', '__ceil__', '__class__', '__delattr__', '__dir__', ... ]

PS: I will never get away from the fact that user-space memory addresses are also basically keys into the page table, so it is hashtables all the way down - you cannot escape them.

I have begun to see that YT is being hostile to adblocker users - and this worries me. I assume YT is already probing the clients to see which are circumveting the ads.

I had an (let’s say unconventional) idea at one point: an add-on which only purpose is to show the YT ads in the background which uBO blocked. All of the blocked ads would be played (eventually) - except that the user can just ignore this happening in background and wouldn’t be actually seeing the ads. I.e. the browser would just move playing the ads into a background container not visible to the user.

Jokes on merge… when a rebase editing goes wrong after +15 commits and six hours, and git hits you with a leadpipe: “do it. Do it again, or reassemble your branch from the reflog.” I.e. you commited a change very early, went over bunch of commits resolving/fixing/improving them and at middle way forget if you should commit --amend or rebase --continue to move forward. Choose wrong, and two large change-sets get irreversilbly squashed together (that absolutely shouldn’t), with no way to undo. Cheers. 👍

The default systemd target to boot into can be overriden from the kernel command line.

If the GUI ever gets broken, having a such fallback boot entry just for the (VT) console mode is invaluable. (The boot-entry can reuse the same kernel and initrd images from the regular boot.)

I never finished reading my CMake book that weights about two kilos. It’s now outdated, except for the core concepts.

I tried Luks and BTRFS more than 6 times leading to a script error each and every time.

This was actually my experience also, so I went back to a manual install to just get it done. I think the archinstall script won’t get any configuration of device-mapper/LVM right (including disk encryption with cryptsetup). The disk encrypt setup had even more hoops to go through than just LVM.

Why would learning be gatekeeping? I wish I could just teach my secrets… The manuals are only a shallow guide to knowledge. E.g. ls, has condensed for me to ls -laR mostly, and that ls<tab> usually gives tools that list something. ch<tab> gives tools to “change something”, like chmod. mk<tab> to “create something” mkdir etc.

I may navigate in the terminal, but putting me at front of Blender etc. and I’m back to crawling speed of RTFM, and all I would see is a zoo of buttons.