I think it makes sense in two ways: Some people in right-wing world think that women are property, without individual agency. If another man has been able to have sex with her, you have failed as a Real Man™ to protect what’s rightfully yours, in the same way as you have failed if a fox gets into the henhouse.

Or, a Real Man™ is so good at sex that his wife doesn’t want anybody else. Either way, being a “cuck” means you’re not a Real Man™.

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.

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.

According to the ConnectBot issue tracker, it’s not possible to retrieve the private key that it created. You’ll have to make a new key pair, and share the new public key with tildes. The keys are randomly-generated, so the new pair will be different, regardless of whether you use the same password.

According to Merriam-Webster, the word “veteran” comes from a Latin adjective, veteranus, describing long experience. The first known use in English carried the meaning of an old soldier who served for a long time. But okay, let’s pretend that the original meaning isn’t valid because it was borrowed as a word describing a soldier, then shouldn’t we also go after people who call themselves “veterans” because they spent a single term of enlistment in the armed forces, and especially those who never had a tour of duty?

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.

Hey, all you folks ought to get together and publish a guide to writing good FOSS documentation,

It was enjoyable, I laughed a bunch. The ridiculous justification for returning to Old West conditions in 3023 was reasonably clever, as was the 3D standoff/gunfight. I watched too much Archer, though, and got annoyed by the six-guns firing dozens of rounds.

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?

Lemmy feels so much like the early IRC or Fark days. In '93, if you were in a chat system, there was a damned good chance you were nerdy college student.

It’s possible that you were a horny college student, and then you’d be on ISCA BBS.

It doesn’t have to be a seismic shift. Geocities and Angelfire (still around. BTW) were corporate, they needed to make money, and when the free web hosting somehow failed to make money, the corporate owners shut them down.

The Fediverse is decentralized. It doesn’t have to get huge, or make a lot of money. It can carry on for as long as it has enough users to carry on. Heck, the biggest BBS that I used back in the day had 23 phone lines. Several hundred regular users, but only 23 could connect at a time. It even survived a few years into the Internet era.

That is to say that Lemmings don’t have to ‘win’ some sort of imaginary competition by taking all of the users from the other site. People used and enjoyed those bygone systems while they lasted, and we can do the same.