Case-sensitive is easier to implement; it’s just a string of bytes. Case-insensitive requires a lot of code to get right, since it has to interpret symbols that make sense to humans. So, something over wondered about:

That’s not hard for ASCII, but what about Unicode? Is the precomposed ç treated the same lexically and by the API as Latin capital letter c + combining cedilla? Does the OS normalize all of one form to the other? Is ß the same as SS? What about alternate glyphs, like half width or full width forms? Is it i18n-sensitive, so that, say, E and É are treated the same in French localization? Are Katakana and Hiragana characters equivalent?

I dunno, as a long-time Unix and Linux user, I haven’t tried these things, but it seems odd to me to build a set of character equivalences into the filesystem code, unless you’re going to do do all of them. (But then, they’re idiosyncratic and may conflict between languages, like how ö is its letter in the Swedish alphabet.)

How about a government-sponsored, non-profit authentication service? That is, it should be impossible to get a loan, open a line of credit, or anything else in somebody’s name, without the lending institution verifying that it’s actually on behalf of the named individual. Eliminate the security-through-obscurity technique of using bits of easily-leaked personal information as a poor substitute for actual authentication.

I mean, (as a comparative example) I have to go through an OAuth2 consent dialog to connect a third-party app to my email account, yet somebody can saddle me with huge debts based on knowing a 9-digit number that just about everybody knows? It’s the system that’s broken, tightening up the laws on PII is just a band-aid.

Sorry, that I’m not certain of, since that’s an installer-specific thing. I think I’d try that option first, and see if the installer lets you choose the empty drive.

Just spitballing here, but if I read this correctly, you pulled the Windows drive, installed Mint, and then put the Windows drive back in alongside the Mint drive? If so, that might be the issue.

UEFI firmware looks for a special EFI partition on the boot drive, and loads the operating system’s own bootloader from there. The Windows drive has one. When you pulled the Windows drive to install Mint on another drive, Mint had to create an EFI partition on its disk to store its bootloader.

Then, when you put the Windows disk back in, there were two EFI partitions. Perhaps the UEFI firmware was looking for the Windows bootloader in the EFI partition on the Mint disk. It would of course not find it there. In my experience, Windows recovery is utterly useless in fixing EFI boot issues.

It’s possible to rebuild the Windows EFI bootloader files manually, but since you don’t mind blowing away both OS installs, I’d say just install Mint on the second drive while both of them are installed in the system, so the installer puts the Mint bootloader on the same EFI partition as the Windows one. With the advent of EFI, Windows will still sometimes blow away a Linux bootloader, but Linux installers are very good at installing alongside Windows. If it does get stuffed up, there’s a utility called Boot-Repair, that you can put on a USB disk, that works a lot better than Windows recovery.

Paved roads don’t just naturally occur, though. That lifestyle is already an insane prospect, unsustainabke but for the large tax subsidy required to enable it.

I live in the U.S. That comment is 100% true, no matter where one lives.

This is madness, but since this is a hobby project and not a production server, there is a way:

• Shrink the filesystems on the existing disks to free up as much space as possible, and shrink their partitions.
• Add a new partition to each of the three disks, and make a RAID5 volume from those partitions.
• Move as many files as possible to the new RAID5 volume to free up space in the old filesystems.
• Shrink the old filesystems/partitions again.
• Expand each RAID component partition one at a time by removing it from the array, resizing it into the empty space, and re-adding it to the array, giving plenty of time for the array to rebuild.
• Move files, shrink the old partitions, and expand the new array partitions as many times as needed until all the files are moved.

This could take several days to accomplish, because of the RAID5 rebuild times. The less free space, the more iterations and the longer it will take.

If you can assign a second IP address to the network interface, then just do so, and bind the docker container to one, and Adguard Home to the other. Otherwise, the reverse proxy based on the server name is the way.

This just sounds like a bad idea, a solution in search of a problem. Sure, sudo is a setuid binary, but it’s a fairly simple program, and at some point, you have to trust the code. It’s also a very fundamental piece of the system that you want to always work, even (especially!) when other things get borked. The brief description of run0 already has too many potential points of failure.

100%

Nah, Linux is confusing because it’s software. I have a well-paying job in large part because Windows and macOS are confusing as hell, too.

I feel this in my soul, except about Windows. I’ve got a handful of machines at work that refuse to update to Windows 10 22H2. They give an error code during the compatibility check. Googling that error code returns dozens of forum posts with hundreds of users and “Microsoft support agents” chiming in. They give the same list of suggestions—that don’t work—to fix it. Nobody can say what the error code means, or what the compatibility check checks. The official Microsoft fix is to reinstall.

I don’t want to reinstall. The suite of software these computers run would take several hours to reinstall.

This is typical of my experience with Windows. (I’m a Unix/Linux guy.) I look up how to do something in Windows, and with the official Microsoft documentation, one of three things inevitably happens:

1. I follow the steps and click the things, and it still doesn’t work.
2. I can’t follow the steps because one of the things to click is greyed out for some reason.
3. I can’t follow the steps because the documentation refers to an older edition, and Microsoft has removed one of the things to click.

One time, when trying to get Excel to run a mail merge, I ran into all three problems in three attempts.

The same happens with 3rd party sites. They never say the edition of Windows to which their guide refers, and the feature is deprecated or gone. (Most recently it was about getting a Windows 10 start menu behavior back on 11.)

Oh, and since Windows is mainstream, a lot of the information is in the form of AI vomit, and covered in ads and dark patterns.

Honestly, I can’t make head or tail of this description. It doesn’t matter where the network devices are physically located; what’s the layer 2 topology?

It always had those dependencies, they’re part of the base desktop system. It’s just that the Chromium package from the unstable branch depends on packages from the unstable branch. The unstable versions got updated so they are no longer the same as the stable packages, and apt has to uninstall the stable versions of them to install the new unstable versions.

Could try the *arr software.

Haha, do you ever feel like the last one to get the joke? I do sometimes.

I’m not the only one! It doesn’t work with my sound bar, and the developers think that editing 3 (!) obscure config files is an acceptable workaround.

This question has really got me thinking about the old days! I thought that it was looking into Debian Linux when trying to repurpose some old IBM PS/2 machines at work, because there were rumors of patchsets for the Linux kernel to support the MicroChannel Architecture bus and ESDI drives. But now I remember that it was actually GeekGadgets, a Unix environment for Amiga based around the ixemul.library. That’s where I first read the GPL, and admired its legal Jiu-Jitsu of using copyright laws to ensure freedom.

I’ve never been a Windows user on my own machines as a result. I just went from Amiga, to FreeBSD, to Ubuntu.

There’s a lot of love for it here, so I guess my experience isn’t typical. I updated to Ubuntu Lunar Lobster on my home media machine, which comes with PipeWire by default, and it’s utter shit. The vocals and some instruments in my music tracks only play nearly inaudibly from the center channel of my 5.1 surround system. It’s unlistenable, even with the center volume boosted.

Seriously, what am I missing? How can it do audio that poorly?