h0rnman

C64 gang, represent!

Seriously though, I feel like that generation of machines was the last time you could look at hardware and say "yeah, I understand literally everything about how this works" and that knowledge has made even some of my (tech sector) coworkers think I'm a wizard

One i haven't seen yet - Marilyn Monbroe

Edit: Annie Broakely

Brothello

Broatmeal

I guess man, I'm just trying to offer alternatives. We travel enough that we like knowing what we're gonna get instead of having to worry if we're going to be the next horror story. The airbnb app makes a point now of assuring you that the price you see is all-inclusive of fees - now why would they do that, I wonder. Ultimately, we're probably some of the tidiest travelers. We just don't have time to worry about rules changing at each place depending on how badly the host wants to pocket that cleaning fee

After chores, cleaning fees, and non-refundable deposits, is it really though?

What you're looking for is anything labeled a "suite". I prefer to stay in those whenever possible, and generally use Staybridge, but there's other options out there

Still a long way until the end of November...

Appx and UWP are more packaging (like rpm, deb, msi) formats than an executable format. PE is behind everything in windows and the amount of effort required to change that seems truly Herculean, even for an organization the size of Microsoft. Heck, even executables for windows ARM were PE (as well as UEFI binaries). But even if you assume that they do go forward with something that insane, if they want developers to write software for it, they'll have to publish the format specs so that gcc and llvm can implement them so that the tens of thousands of existing libraries could be ported

Yeah but given that dxvk is a thing, a switch to dx13 would just need to be implemented there. The underlying wine layer would only need to change if the PE format changed. But even then, that would destroy backwards compatibility in the windows world.... something that Microsoft's enterprise customers would (rightfully) crucify them for.

Sab might have its own mask settings - it would be worth looking at. Same thing applies here - subtract the mask part from 7 to get the real permissions. In this case, mask 002 translates into 775. This gives the uid and gid that the container is running under (probably defined in a variable somewhere) Read/Write/Execute, but anyone else Read/Execute. The "anyone else" would just be any account on the system (regardless of access method) that didn't match on the actual uid or gid value.

For what it's worth, Ikea's LACK tables make great mini racks

Could be that lidarr is setting its own permissions for downloaded stuff (look for something like dmask or fmask in the docker config). You might also need to chmod -R so it hits all sub folders. If you have a file or directory mask option, remember that they're inverse, so instead of 777, you'd do 000 for rwxrwxrwx.

The article you're looking for is in Dragon #62 - The half-orc point of view. There's a whole series of them and they're all good reads.