![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
There is a lot of advice in this thread warning you about doing this. Please heed it. Instead, read more about how permissions and file ownership works.
There is a lot of advice in this thread warning you about doing this. Please heed it. Instead, read more about how permissions and file ownership works.
No proper estimate of download size.
Please work on tab grouping instead!
I would have a look at mutt’s patterns in your position.
Besides macros, I think vim had some other relevant feature for this. Just can’t remember it right now.
This is why regulation is a good thing.
This is the way.
Nothing comes even close. I just wish there was a distributed / mobile-enabled way to use org-mode. I guess there exists some project, but running full emacs org-mode mobile is hardly usable.
Any issues with home manager?
Use Ansible for package installations and configuration, and a git repository & GNU stow for dotfiles.
Try having unattended-upgrades
with a rolling distro.
Not worth the trouble. Options are either to run a permanent X session somewhere, or a VM with suspend to disk.
Good job, Mullvad!
Now add port forwarding back.
Reading a blog post is more accessible than reading a man page.
I don’t agree with that assessment at all. People should learn to read manpages, instead of being spoon-fed pieces of manpages in inferior form.
Passwords will be brute forced if it can be done offline.
Private SSH keys should never leave a machine. If a key gets compromised without you knowing, in worst case you will revoke the access it has once the machine’s lifespan is over. If you copy around one key, it may get compromised on any of the systems, and you will never revoke the access it has.
And you may not want to give all systems the same access everywhere. With one key per machine, you can have more granularity for access.
What’s your threat model?
Personally I think full disk encryption with LUKS is the only worthwhile setup. Directory-based encryption software tends to be error-prone, and is much more vulnerable.
But those keybindings usually control flow…
If you care, please take time to upvote or file bugs on packages that don’t follow XDG. Or even better, make PRs.
Is there any good explanation of this somewhere?
For servers stability is most important, so Debian.
We run production loads on 2.6 kernel. Please don’t ask questions.