

I do this exact same expression when I’m forced to gain knowledge of something potentially personally catastrophic…
I mean no harm.
I do this exact same expression when I’m forced to gain knowledge of something potentially personally catastrophic…
This was truly a wtf moment of the month.
Last time I spent time watching him was when he freaking fixed the kexec syscall for IBM PowerPCs. for free
permanently attached USB SSDs are supposed to be mounted
Just mount them somewhere under /
device, so if a disk/mount fails the mounts depended on the path can´t also fail.
I keep my permanent mounts at /media/
and I have a udev rule, that all auto mounted media goes there, so /mnt
stays empty. A funny case is that my projects BTRFS sub-volume also is mounted this way, although it is technically on the same device.
For example, the new .config directory in the home directory.
I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf
(or even worse in a program specific ~/.thisapp/
;
The ~/.config/
scheme works as long as the programs don’t repeat the bad way of dumping files as ~/.config/thisconfig.txt
. (I’m looking at you kde folks…) A unique dir in .config directory should be mandatory.
If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier.
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 point when the AI hallucinations become useful is the point where I raise my eye brows. This not one of those.