All the core tools are actually a single executable with many symlinks to it, which makes the distro very compact. This makes it very nice as a base for Docker images.

https://en.m.wikipedia.org/wiki/BusyBox

Thing is there will always be these sorts of features that are initially only supported on Windows as long as Linux is not a priority platform. So there will always be excuses to not switch :(

Late to the party, but I remembered this talk about maintaining a FreeBSD fork. If you want to get a more detailed description of what maintaining a customized OS entails, I encourage you to watch it: https://youtu.be/xddAX6L3iWc

Nice, glad to help!

As for the automatic restarting, the whole Docker container exits, if the main process (specified as CMD in the Dockerfile) exits (in this case the minecraft server) and Synology probably auto-restarts the containers on exit by default.

Check this out: https://stackoverflow.com/a/62142025

So adapted for your requirements:

echo '/stop' | socat EXEC:"docker attach mcbe-world",pty STDIN

AFAIK /stop is not just a shell command, it needs to be given to stdin of the minecraft process. The broader question here is how to pass something to stdin of a running process.

As I see it their options are:

1. Copy it without meaningfully changing anything, i.e. just redistributing Debian or Ubuntu with some logos and desktop backgrounds - there is no reason to install this on your own and no one will care. This is effectively the same thing as customized Windows installs that they ship.

2. Creating a custom Linux distribution. This is feasible and has already been done (System76 created Pop_OS! based on Ubuntu; Android and ChomeOS are essentially new Linux distributions built from the ground up, taking only the kernel and ignoring the existing ecosystem), but requires serious maintenance work to be any good and offer real advantages over existing distros.

3. Forking a kernel like Apple did. This has fairly limited purpose from the perspective of laptop and workstation OEMs that use regular off-the-shelf parts. This is usually done to provide support for custom hardware (Apple) or for proprietary software that requires deep integration with the kernel (VMware).

No one will think of option 1 as a serious competitor in the OS market, option 2 requires a ton of work and motivation, and option 3 is useless for these OEMs. Software just isn’t their business and a cheap copy offers no real advantages over shipping an existing thing.

The name Linux is trademarked, so you cannot use it without permission, yes: https://www.linuxfoundation.org/legal/trademark-usage

But other than renaming it for trademark reasons, there are no real requirements for making improvements or whatever.

The open source licences of Linux and the BSDs allow verbatim copying. That’s kind of the point of OSS.

In fact, Mac OS is a verbatim copy of a BSD.

Sure, for some produce that is true, I am aware. But tomatoes? At least where I’m from they are either local or come from other EU countries (Spain, The Netherlands usually).

Where the fuck do you think people buy tomatos?

#define is not an import

This is AMD64 - extensions to x86_64/AMD64 are created all the time, after a while they become expected by software distributors and compiled software relies on their existence. That’s why new games don’t work on old CPUs.