willybe

I take it schools aren't teaching tech literacy. We wouldn't want the kids to get in the way of our overlord marketing agencies.

Like a Bosch!

Keep this quiet, but VPN to UK and sign up for channel 4. They have commercials, but UK does much funnier commercials than across the pond.

Docker is a moderately sized step beyond VM.

I might recommend setting up VMs with something easy like VirtuaBox. When you have that figured out move on to Docker.

If your a casual user VMs are likely sufficient.

I used awk to migrate users from one system to another. I created template scripts for setting up the user in the new system, I dumped the data from the old system, then used awk to process the dump and create scripts for each user in the new system. That was a fun project.

When you have battery life beyond 5s next year you'll be thankful

Yeah, I'm sorry to say that is a result of good marketing. I work at a university and we have experience with a good number of XPS laptops.

We saw at least a 60% problem rate, and Dell's support was dog slow. Batteries being the weak spot. Because it's thin it is more fragile, we saw a number of broken screens, and keyboards. One survived a Gatorade spill, but another failed after a water spill. Go figure

A three year warranty helped, but we were out of a laptop for months at a time, more than once on the same laptop.

Ultra thin laptops look cool, but suck in almost every other way. If you need thin then get a MacBook Air.

can threads users follow me?

Match blocks allow you to restrict who/what is allowed or not allowed to connect to the server. There is a large number of options to utilize. Put this near the bottom of sshd_config. There should be an example there.

Here are some more examples: https://stackoverflow.com/questions/10829712/sshd-with-multiple-match-sections-override-settings

Yes that's the right way to block root login. An added filter you can use the 'match' config expression to filter logins even further.

If you're on the open network, your connection will be heavily hit with login attempts. That is normal. But using another service like Fail2Ban will stop repeated hits to your host.

~~Ssh listens on port 22, as soon as a connection is made the host moves the connection to another port to free up 22 for other new connections.~~ Btw: I wasn't thinking clearly here. Out going connections won't be using port 22, but the listening incoming port is always 22.

This is the way.

AKA don't be this guy.

Don't trust executables on your computer. A Windows VM in a Linux host that you revert to a prior snapshot of you're really curious.