amigan

Interesting. Reminds me of PC/IX, and it probably similarly doesn’t even enter pm, judging from it running also on an 8086.

286 Protected Mode is very different from 386 PM and there is no way Linux will would run on it.

Preach it.

“Different inode” means a different file entirely, not necessarily its majorminor:inode tuple resolved through bind mounts/overlayFS/whatever. I’m saying that if you have containers using even slightly different base images, you effectively have n copies of libc in memory at once on the same system, which does not happen when you do not use containers.

Except each container has its own libc and any other dependencies. If any linked binary or library has a different inode, it gets loaded separately. I would say it is indeed quite similar, even if the images in question here aren’t hundreds of megabytes in size like with Electron.

It seems every new shiny technology today tries its darndest to short-circuit 40+ years of advances in OS virtual memory design. Between Electron and Docker, the entire idea of loading an image into memory once and sharing its pages among hundreds of processes is basically dead. But at least there’s lower support burden!!!1111

I used to have everything backed up to a 2TB USB drive. Which I accidentally dropped down the stairs. I lost thousands of family photos and documents. That changed my backup perspective.

If it’s the only copy, it’s not a backup. It’s the master.

I am mistaken. It now uses .NET Core, but before it used to use Mono as the .NET runtime. Either way, both are pigs.

I would switch in a heartbeat if it didn’t use .NET. Plex is a giant heap of trash, but at least it doesn’t eat RAM.