I hope it works out as a positive experience for you.

Interesting for KGLW since they live stream concerts and have released an album for free. I didn’t know that they did that with Spotify.

Serious question: don’t the artists have the ability to remove their music from Spotify if the deal is so bad? Are they leaving it there for exposure, or does the label require that they publish on Spotify?

How many gamers today have even played or know what the original Rogue is?

As you mentioned, Alice’s Restaurant. I used to listen to that every year on the drive to my grandparents’ house for Thanksgiving dinner.

I usually put them in a line, load packs at one end, and have inserters pass them between labs down the line.

VACUUM FULL ANALYZE

Scooby Doo!

The key enrollment that Mint did sounds like registering the Machine Owner Key (MOK). That basically tells the bios that anything signed with that key should be permitted. The MOK is especially required when compiling your own drivers. Anything shipped by a Linux distro should already be signed so that the shim will permit it. SecureBoot is more about making sure your boot files haven’t been tampered with rather than being about preventing the owner from doing something.

You should already be able to boot any modern Linux OS that has support for SecureBoot. Only if you compile your own drivers or kernel would you need to use a MOK. If you do need that, you should be able to enroll another MOK or copy the MOK key files from the Mint install and use those keys to sign drivers in any other Linux distro.

The cli program mokutil will let you view and export your enrolled MOKs.

Text would be more useful than screenshots. Text is smaller to store, easier to translate, and easier to shape to whatever screen a person is using. :)

The MOK key stuff is fixable, but it sounds like you don’t have a big need for SecureBoot in the first place. I would say leave it disabled for now.

Also, SecureBoot is more of a way to authenticate the software that is being loaded at boot time. It could prevent someone from inserting something bad at boot time. It’s nice to have but not required.

Further, I think your EFI Boot Manager has a BootNext entry that is booting the MOK utility instead of the Linux shim or kernel. You should be able to remove this BootNext entry in your EFI settings.

If you can get it booted into Linux from a bootable USB drive, you can use the “efibootmgr” program to inspect and remove the BootNext entry.

sudo efibootmgr

will show you all of the EFI boot entries. If the first line says BootNext, then that’s likely the problem. Note that these are not grub boot entries. The EFI has a boot list that happens before grub.

sudo efibootmgr —delete-bootnext

will remove the temporary BootNext entry.

After that, make sure secure boot is disabled and you should be able to boot Linux.

This page https://wiki.debian.org/SecureBoot#DKMS_and_Secure_Boot Mentions the “MOK Manager EFI Utility”. That utility is the blue screens you posted. You should be able to change a setting in EFI to boot something other than the MOK Manager.

Can you turn off Secure Boot in your BIOS/EFI? That should get you booting again, and then you can figure out the MOK.

Another thing to check is that your EFI is actually booting the Linux kernel. It could be booting the MOK enrollment program which runs only at boot time. There should be a selection in the EFI settings that mentions “next boot” or something like that.

Use brew to update the core Unix utils such as bash, tar, sed, etc to the latest GNU releases. The mac has really outdated BSD-based versions.

I hope they have a good way of keeping rainwater out of the bins.

Emacs Org Mode would be perfect, but that’s a commitment if you don’t already know Emacs.

Also https://mcfunley.com/choose-boring-technology

It’s common in the US Tech industry. It’s considered “voluntary” because you could always say no and find a different job, or you could negotiate the removal of that clause. Often at the beginning they give you an opportunity to list your existing obligations that would be exempted. Always read the fine print of your employment agreement.