#TIL if you are going to drink a dark roast ice coffee, don't eat deli roast beef with spicy mustard and mayo immediately before it. The taste is incredibly #funky and #jarring.

#coffee #darkroast

#TIL band Cornershop were burning posters of Morrissey in protest at his racism all the way back in 1992.

https://www.cornershop.com/tags/burning-morrissey-poster

https://www.theguardian.com/music/2019/may/30/bigmouth-strikes-again-morrissey-songs-loneliness-shyness-misfits-far-right-party-tonight-show-jimmy-fallon

#UKpol #Morrissey #Cornershop #Racism

#TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).

The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.

https://elm-chan.org/docs/fat_e.html#fat_determination

However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.

https://github.com/torvalds/linux/blob/1590cf0329716306e948a8fc29f1d3ee87d3989f/fs/fat/inode.c#L1675-L1680

Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!

#TIL I've recently learned that you can use #Bitwarden as your #ssh agent. In other words, it can both store ssh keys and use them with quite a simple integration. I've tested this workflow with both Flatpak and Snap versions of Bitwarden. Now I can securely sync my keys between devices 🔑

I was going to facetiously post a few paragraphs of Lorem Ipsum #today but then went down the rabbit hole of learning its #history. Oh boy.

It's quite fascinating that it's not just #typography #placeholder #text. It actually comes from an #ancient #Latin #text dating back to 45 BC by the #Roman #statesman and #philosopher #Cicero. The title of the text was "De finibus bonorum et malorum" and it was about #ethics and #pleasure. It was mistranslated years later and used as #dummy text since around the 1500s.

https://www.britannica.com/topic/Lorem-ipsum

#til #loremipsum #post

I use FreeBSD jails more way over a decade now. Today I learned, that I can simply do “jexec $jail_name” without a parameter and get a sh shell in the jail. You don’t actually need to put “sh” at the end of the command 🤯😂

#freebsd #jails #til

It made me really appreciate the composability of CLI when I could type git remote add forgejo .../$(basename $(pwd)).git && git push ... to get that micro-automation going.

#TIL

Same thing happened to me with #git and Linux earlier. Now that I think about it, I'm surprised I learned gdb CLI so late.

The original is written in #OCaml with quite involved setup, but #TIL about two single-executable #Rust implementations: Kodama and Weibian.

I'm still trying them out, but luckily both support @typst@mastodon.social so at least I can keep a common content format between them and final document

Trzy razy się przeprowadzić to jak raz spalić

Moving thrice is like having one fire