well, actually the 6.5% have better privacy settings, as they are in a larger crowd than the 5.4% "unknown" users.
So they are more interchangeable than the "unknown" Users
There are some really mixed answers here. I would stick to the mainline distros and not go for a fork with a few customizations. It does depend on what you want, especially if you are willing to learn using the terminal and if you want bleeding edge or more stability. My list would be:
Debian
Kubuntu
Fedora
Pop!_OS
Arch Linux (If you want to learn Linux from its fundamentals)
So, one use case would be saving your current terminal setup. Instead of exiting the terminal and navigating to the project and setting up the environment again next time, you can simply detach and re-attach.
It’s a “terminal multiplexer”, i.e. you can start multiple terminals in a single terminal.
You might ask, why not open a new terminal window or tab? Well, you can only do that in a desktop environment and that’s not always available. Even if you can, you might want the terminals to be side by side in a single screen, which might not be easy to do with window tiling.
The real power of tmux, though, is that it manages the session you created. To quote from the manual:
tmux may be detached from a screen and continue running in the background, then later reattached.
So, one use case would be saving your current terminal setup. Instead of exiting the terminal and navigating to the project and setting up the environment again next time, you can simply detach and re-attach.
When connecting to a remote server, this is especially useful:
Each session is persistent and will survive accidental disconnection (such as ssh(1) connection timeout) or intentional detaching
Suppose you want to execute a long running command on a remote server. If you just put it to foreground, when you exit the ssh session, the job is also killed. If you put it to the background, its output can’t be easily observed.
With tmux, you can simply run it in the foreground like normal and detach. When you reattach later, the job is running and you get all the output easily, as if you have been in that session all along.
The real power of tmux, though, is that it manages the session you created.
So, one use case would be saving your current terminal setup. Instead of exiting the terminal and navigating to the project and setting up the environment again next time, you can simply detach and re-attach.
In the company I work, we have to use jumpbox + “password” from proprietary code generator.
Imagine going through this, then you suddenly need 2nd terminal. Inconvenience doing it again in another terminal?
Well, there is a solution:
tmux
CTRL+B then ". And now you have 2 terminals.
Also tmux is great for “quick solution” kind of things - to leave something running in the background. Talking about background - you can have many terminals open, from only 1 SSH session. :)
Just to add, if you wanted to start VPN on boot automatically, you can create a systemd service file to take care of that and put it in ~/.config/systemd/user/
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.