...you're going to have a bad time.
FWIW, I use Slack for work, and I find it really useful. It's a pretty good way to connect normal email, github emails, and chat.
My only real beef with Slack is that its markdown language is a bit different than, and inferior to, Github's. Which is an annoyance when, for example, github markdown messages are rendered by Slack.
.. to know how people feel.
We, as members of society, need information when we choose who to befriend, who to do business with, and who to avoid. If people are not free to express themselves, we cannot make good choices.
If you're the type to avoid humor in bad taste, and you find this person offensive, you should be fighting this. Otherwise, at some point, you may find yourself emotionally attached to someone who feels this way, only to find out after the fact. When people bare their soul in a public forum, without fear of repercussion, you can observe and make decisions on how you want to interact with them in private. You can decide ahead of time.
If speaking one's mind is potentially illegal, much important information becomes unavailable as people will be unwilling to speak their minds. You cannot know someone is a racist, or someone is opposed to religious influence, or someone is against liberal governance, or someone has a problem with war. You can't know if they're neo-nazis, and you can't know if they believe politicians should be hanged for war crimes.
You may enter into relationships with these people only to find out much later that they feel a certain way.
The more deeply offended you are by speech, the more you should fight for it to be open and free.
One person doing something does not meant that the 50% of the population who share her gender is dishonest.
For a moment I read that as "does not meant that the 50% of the population who share his gender.." and thought you were commenting about the absurdity of the broad-based accusations that men in general are the problem.
Then I re-read and realized you were just being disingenuous.
How about not inventing an entire 45 minute scenario with the Dwarves in the mountain running from Smaug?
As I recall the extent of what happened in the mountain was Bilbo was a sneaky thief, and the dragon flew out to torch the town. How exactly was the story enriched by the hairbrained scheme to drown the dragon in gold?
While this is true, the attacker does not need physical access for this. All they need is access to an innocent user who can be convinced to plug something in.
The FBI and secret service demonstrated this type of attack back in the early 2000s. They dropped usb drives near banks night drop boxes and front doors that pinged a server with the local ip and machine name and wrote a file locally when plugged in with the autorun on. Something like 70% or so pinged. People where plugging them in to try to figure out who's they were to return them.
Its pretty easy to convince someone to plug something in.
That tugboat you call a mouse and the GUI are fine for your desktop, but if I see xorg installed on servers under my control I remove it.
And if the server doesnt have xorg, the discussion is moot. For those that do however, it might as well also have NetworkManager as it makes life simpler.
Obviously I use ssh for most linux connections, but there are times where there is a GUI.
I missed the part where it is illegal for a state actor to lie when not under oath.
ifconfig doesnt persist changes. Thats also not made obvious to the unfamiliar.
Gotchas like that are why you need NetworkManager.
Is there anything Unix about Gnome? How exactly is this a useful criticism?
Theres also nothing Unix about HTML, or CSS; maybe you're on the wrong website, Geocites is that way.
If you can explain the logic why this order went out, I would love to understand it.
I can't explain it. Such apparent idiocy was a major factor in me leaving the DoD.
Did they actual show you how it violated those terms, or was it just a vague threat?
It was a vague threat, but the DoD can pull a security clearance for various reasons, which means sudden unemployment for the worker. So having ones clearance threatened is akin to be threatened with firing. Except it's a kind of firing that means you can't easily work anywhere else in that "industry" either. So it's a pretty attention-grabbing threat.
But it also shows the absurdity of the DoD leadership. They were specifically saying that people with clearances couldn't see info that everyone else on the planet could see. This kind of insanity was a major factor in me leaving the DoD. The movie "Catch 22" makes a lot more sense after you've worked with those people.
At least in CentOS and RHEL 7, NetworkManager does VLANs and Bonding and bridges in about 2 clicks. Add interface, choose bonding | VLAN | bridge, and go.
bridged VLAN's (yes, those are a thing)
Set up your VLAN interfaces, bridge them. Not seeing the issue.
90% of the other functionality isnt relevant 90% of the time. The point of a GUI is to offer the most common options, and from my usage of NM, it does that admirably.
So sure, if you're a sandwich shop putting a $500 server under the cash register, or you are a teenage college student setting up a video sharing network for your bro's in the flop house you board in, NetworkManager will work fine for you.
What about a network engineer who has better things to do than spend more time researching the syntax for setting up tagging on a single node than it took to set up the switch infrastructure?
As someone who is deeply familiar with networking but only vaguely familiar with Linux's arcane ways of configuring its network-- which apparently change drastically depending on such things as:
* whether you want it to be per-session (ifconfig)
* or persistent (/etc/DependsOnYourDistro/someFiles)
* whether it should actually persist with the interface rather than how the kernel decides to allocate
and so on-- I am quite happy to see NetworkManager. THere is no reason that setting up a bonded or tagged interface should be more complicated than saying it verbally, or why I should have to fall back to CLI in order to do that.
Heres a fun tip: not everyone wants to be a full-time Linux admin devoted to a particular breed of distro. Some of us have a job in supporting a very wide array of systems, and the less arcane black magic we need to learn for each individual system the better. Historically Linux's networking has been AWFUL, as just a few years ago it was considered normal for a box's IP-to-interface mapping change on reboot because apparently its logical that the OS randomly assign interface IDs to physical interfaces, and there were roughly a hundred different methods and places to configure all of the various networking pieces (resolvers, mac addresses, firewall, bonding, vlans, device/interface mapping).
It boggles my mind that there are people who think that complexity for complexity's sake is a good thing. CLI is wonderful for batch operations that you do every day. GUI is wonderful for things you will do once a month, and dont want to use mental bandwidth for remembering a command.
Assuming he thought this through, does that mean the US law is against the people knowing what their government is doing?
When I worked for the DoD, we were cautioned to not read newspaper pieces describing what Snowden revealed, because it violated the terms of our security clearances.