duncesplayed

Just an FYI that at this rate it's only going to take another 115 years before Linux has 100% market share.

Indeed. Licensing usage of something is antithetical to free software culture anyway. It would violate the Free Software Foundation's Freedom Zero, that you should never have to accept a licence to use something. (This is why free software cannot ever have a EULA, for instance)

chess.com has cute profile pictures for its bots. Bullying "Martin" is just scientifically more fun than bullying "Stockfish Level 1".

Trump already has a mate, though! So what's his excuse?

That is not what happened at all. Foudouko (the murdered chimp) used to be the leader of the group, but there was a power struggle in 2007. Foudouko's right-hand man was injured on a hunting trip, and so, in terms of physical/military might, Foudouko was more or less on his own. There was a (successful) coup from a younger male who took advantage of the timing, and Foudouko was ex-communicated

I think Foudouko gave up on trying to regain the alpha position, but he kept trying to rejoin the group (always unsuccessfully) because it was the only way he could find a mate. In 2017, finally the group had had enough of him constantly trying to elbow his way back into the group, and just decided to murder and eat him.

It has nothing to do with resource-hoarding and is a very unique situation. In fact it's the only documented case ever of a chimp group murdering someone from their own (former) group.

What advantages does it provide

ZFS, mostly. There are some smaller peripheral things (like much better manpages), but these days the big one is probably ZFS. Zero licensing conflicts allows it to be an integral part of the kernel.

It's a bit more complicated than that. System load is a count of how many processes are in an R state (either "R"unning or "R"eady). If a process does disk I/O or accesses the network, that is not counted towards load, because as soon as it makes a system call, it's now in an S (or D) state instead of an R state.

But disk I/O does affect it, which makes it a bit tricky. You mentioned swapping. Swapping's partner in crime, memory-mapped files, also contribute. In both of those cases, a process tries to access memory (without making a system call) that the kernel needs to do work to resolve, so the process stays in an R state.

I can't think of a common situation where network activity could contribute to load, though. If your swap device is mounted over NFS maybe?

Anyway, generally load is measuring CPU usage, but if you have high disk usage elsewhere (which is not counted directly) and are under high memory pressure, that can contribute to load. If you're seeing a high load with low CPU utilization, that's almost always due to high memory pressure, which can cause both swapping and filesystem cache drops.

I'll go against the grain and say that's cool as heck! Wikipedia says the designer (the guy flying/driving it, I think) has been working on it since the 80s. I like people passionate about their hobbies.

Keep in mind that the tar "manual" does not actually call itself a "manual": it refers to itself as a "book". It has 20 pages of preamble (5 title pages, discussions of the authors, descriptions of the intended audience, etc.) It has another 20 pages elaborating on important structs in the tar source code. The licence takes up another 10 pages. The index at the end is 25 pages long.

It doesn't change the larger point that GNU is way bigger than Linux, though. There are a tonne of things that are larger than Linux, and GNU is one of them.

The Villages ~~and their sky-high STD rate~~ would beg to differ. (Edit: apparently that's just an urban legend. Still, old people in The Villages are very social)