To be even more explicit on the last point, that means regularly updating OpenWRT and all your containers, not just the server’s base OS

deleted by creator

Vested interest? Literally vested stock options. Well, by now they’ve already been used to purchase stock.

Not true.

He can’t prevent anyone that received the code under the GPL from using (and distributing it) under the old license. He also can’t relicense code that he received under the GPL only under the new license.

If he receives a new license from the other contributors to distribute under a more restrictive license, he can do that because he has a dual license to the code and is not relying on the GPL for his right to distribute.

Gonna have to disagree with #3 - stopping Vim is not necessary for this. There’s the builtin :! command.

Don’t forget /auto, for things that get automatically mounted when you first access them (autofs)

Not completely ignoring - I assume that was the swipe about “only engages in genocide reluctantly” was about.

Myself, I agree with you that we haven’t seen much sign of that reluctance.

Favorite would be a highly customized zsh.

fizsh (not fish) is what I actually end up using, as I can’t be bothered to copy that config around and retune it for each machine. Gives me the syntactic sugar of zsh with common default options on by default, an OK default prompt, and doesn’t break POSIX assumptions like fish. Also Installs quickly from the package manager without needing to run through the zsh setup each time - unlike oh-my-zsh. And if I still need customization, all the zsh options are still there.

Notify the maintainer of the open source tool - they’re in the best position to push for compliance. They have the power to revoke the company’s license.

And not subject to compliance based retention standards