> Your organizational skills are quite a bit above average.

And that, in and of itself, is very sad and telling of the lack of basic education people are getting anymore. I'm Gen-X and went to a private school (after starting in public and our parents seeing how much that system was already failing back in the 1970s) and we did things there like having some basic monetary education in the 8th grade. We were each given a mimeograph (ah, the smell) set of checks, then we each drew our "job" from a random list and had to do simple budgets based on said income. I'll never forget that the Doctor made a "massive" $75k in 1987 (though the values we were using were already quite old).

Late to the party but..

Here's my entirely personal opinion/experience with Linux Enterprise support for the last nearly20 years now (started supporting linux in house in the early 2000s), we were a 99% Solaris house (a few HP-UX) until even our ISVs were saying that everything they were doing was going linux on x86 (then x86_64) as SPARC was quickly falling behind (yet still cost insanely more $).

RedHat: Was SUPER expensive when it first went RHEL. They initially wanted something like $1600/server/year for x86_64 hosts, set based on what MS was asking at the time. They refused to work with us to split up licensing hosts vs paying for support. Granted, I later learned that our rep at the time was a bit of a jerk and it was probably more him vs the company. Everyone I know that uses RHEL in house, pays for a few critical boxes, runs most on the equiv CentOS to save a ton of $. They are stable and do regular releases though.

Ubuntu/Canonical: FAR more interested in being bleeding edge than stable. Is beloved by SW devs, is way too bleeding edge for HW dev use/compute (I support IC design engineers and the ISVs are SUPER slow at adopting releases so Ubuntu is WAY too fast.. they have a hard time keeping up with RHEL/SLES). They're terrible at outputting patches for things like the automounter, often being years (yes, really) behind.

SUSE/SLES: We started working with them right when Novell bought them and they wanted a foot in the door. They were very willing to split up the cost to license running on hosts/CPUs vs paying for support, which made them far more affordable. They go out of their way to help us work with the ISVs whenever possible. The support response times and quality is fantastic (I have a few co-workers who's dealt with all 3 "enterprise" support channels and they all say SUSE is the best, by far).

Honestly RHEL and SUSE are pretty close as far as stability and sticking to release schedules and all, but my own experience has put SUSE on a level above RHEL overall. Sadly I think RH has coasted far too long on the continued belief that "RHEL is _the_ enterprise linux distro that everyone supports." SUSE was the scrappy competition for quite awhile there and had to really fight to stand out and make a bigger name for themselves. I know of at least one massive chip maker that is nearly completely SUSE in house aside from our IC compute farm, but we have this interesting mix where it's:

IC Engineering compute: SLES
SW devs: Ubuntu
Everyone else/corp: CentOS/RHEL

You are only stalked when you pay them the attention they do not deserve...or read their comments actually.

I will never use GPL in any of the software I release.

Why the fuck are you wasting my time? SystemD being forced on all us is like someone coming and saying everyone know has to use lighthttpd and sendmail. Now please do have your bottle of milk and let the adults talk.

I also do not recall Spider Man coercing anyone.

I am not impressed with your command of "Engrish"

Kali is useless by definition.

Have you seen the corresponding binaries size? Anyway, what would it prevent the new binaries accepting both names, and the old and new syntax? Or writing wrappers (not the best idea, but then...)
The old ones are *still* there...for now. They are just not installed by default.

Travelling back in time to do that would be more effective.

Since when netstat or ifconfig are "performance hogs"? You just use them on the odd occasion, or maybe every couple of minutes.

disable all ICMP is not feasible as you will be disabling MTU negotiation and destination unreachable messages. You are essentially breaking the TCP/IP protocol. And if you want the protocol working OK, then people can do traceroute via HTTP messages or ICMP echo and reply.
Or they can do reverse traceroute at least until the border edge of your firewall via an external site.

I can pretty much assure you I am *non native*, and do not live anywhere near an English speaking country.
Nonetheless, a guy that does not understand English, well, he wont have a problem either. He pretty much wont understand it as the rest of the text.
What next, do you want to obliterate Shakespeare works, because a non native won't understand them?

Bah. I reverse engineered the Novell Login program back in the day. Wrote virus-like tech hidden on the PC that intercepted the Login and password requested transparently, and saved the combo to an encrypted file. Had lists of username/passwords of nearly 300 users. In the end, I was not smart to no brag to the wrong persons about it, and also made a few stupid mistakes. If it were today, would be expelled.

mangina alert