Save your sanity and do Settings -> Blocks -> Block instance -> lemmy.ml
I approve this comment.
Save your sanity and do Settings -> Blocks -> Block instance -> lemmy.ml
I approve this comment.
Millenials - Load"$“,8 LIST LOAD"LEISURESUIT*”,8,1 (wait 10 min.) RUN
Even the oldest millennials were just toddlers when the C64 was relevant, so this is not a typical millennial experience at all. It’s really a GenX thing… so once again we are forgotten.
I would say millennials’ computer experience starts in the late DOS/Win3.11 era at the very earliest, but more typically in the Windows 9x and early XP era. So even IRQ/DMA/config.sys/autoexec.bat fuckery is not that typical.
If you rename a file only changing the casing it doesn’t update properly, you need to rename it to something else and back. This is so userfriendly I have been stumped by it multiple times.
To my great surprise, this has been fixed. I don’t know when, but I tried it on my Windows 10 VM and it just worked. Only took them 20 years or so :)
This isn’t “Windows design”… this is just inherited stone age bullshit from the DOS days when the filesystem was FAT16 and all file names were uppercase 8.3.
NTFS is case sensitive in its underlying design, but was made case insensitive by default, yet case preserving, for reasons of backwards compatibility.
If Microsoft has to design something from scratch, without the need for backwards compatibility, they go for case sensitive themselves. For example: Azure Blob Storage has case sensitive file names.
arch-chroot
your mounted root filesystem/boot
mkinitcpio -p linux
Steps 1,2 and 3 are the entry way to solve all “unbootable Arch” problems by the way, presuming you know what needs to be changed to fix it of course.
I know you’re joking around here, but you don’t have to upgrade every two years. You can use an LTS release instead, or, on the opposite of the spectrum, a rolling release.
Release schedule and duration of support should always be factored into the decision of choosing a distro.