I mean no harm.

  • 1 Post
  • 39 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle
  • 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)









  • 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.


  • 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. 👍





  • 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.