Partially same as @yesman@lemmy.world . I used to encrypt both the system, internal storage and removable storage - all with different 35+ char passwords - until I learned how to threat model. Now I only do system encryption on my Laptop and encrypt internal and removable storage only. In the astronomically unlikely event the feds kick down my door for downloading Linux ISOs, I just hit the power button on my rig and the drives are scrambled. As a bonus, my HISTFILEs are unset so history is lost at every logout or any other session restart. Oh, and .bash_logout is set to do a history -c, just in case.
Edit: I see. I don’t. Open your .bashrc (or /etc/profile if you want the settings to apply to all users) with your favorite text editor and add unset HISTFILE to disable automatic saving of command history. Similarly, add history -c to .bash_logout (or to /etc/bash.bash_logout for system wide). Reboot or logout/login or source the above files to apply immediately.
You know that dotfiles (files that begin with a dot) like .zshrc or .bash_logout can contain important scripts or configuration for your system(s). Same with all the configuration files that can be scattered in directories like .config/ or .gnome/.
The “modern” dotfile means a configuration file that has been saved somewhere so that you can make a backup, or have the same dotfiles on all your machines.
It’s usually saved in git and on GitHub, but crazy people have written whole applications to handle those files (https://wiki.archlinux.org/title/Dotfiles#Tools). I like chezmoi, written in Go, but you have others like stow for example. Those applications handle diffs (when a file has been changed, you see the diff, you can save it or reset it), templates, multiple machines, upload to git, etc. Some applications use a hidden git repository for your files, others use hard-links. Last but not least, you can say “here are the files for Windows, and others files for Linux” if you have different machines.
At my last job I stored on GitLab all the ZSH configuration files, CLI applications configuration, and even macOS configuration files that were in my HOME directory. If my machine ever crashed, I would have been able to restore it in a few minutes thanks to chezmoi, like: format computer, install chezmoi and git, reapply all the dotfiles as if nothing happened.
Jesus Christ 😅 I knew what they are, then, without knowing what they’re called. But what on earth is all this managing enthusiasm surrounding them?! 😅 Would one have a 100 versions of the same dotfile or what? Mind you I have three computers, manually manage a handful of dotfiles + having a backup of them. Please explain a scenario where I would need one of those honking management tools. 🥹
But what on earth is all this managing enthusiasm surrounding them
It looks like a fad, but when you use it once you can be hooked. I see this see as an additional step in automation and making sure your computer is properly set up.
Having the same files across all machines is nice, and it’s backed up. You don’t have to think about it every day, at most once a week to check if a file has been changed and not pushed to git.
Most of the time, you want to have the same .zshrc across all Linuxes and Macs. That’s where such a tool can be useful.
Would one have a 100 versions of the same dotfile or what
If it’s in a git repository, the latest commit (transparent if you use a tool) has your files. At most 20 unique files for me but all at the latest “git version.”
Please explain a scenario where I would need one of those honking management tools
If you want to save your dotfiles on git, or if you want to have the same configuration on multiple Linux machines.
I don’t remember the commands but once a week I would do:
chezmoi diff # to check if a dotfile has not been backed up
chezmoi add ... # to add new or modified files
chezmoi git push # to save my modifications
Partially same as @yesman@lemmy.world . I used to encrypt both the system, internal storage and removable storage - all with different 35+ char passwords - until I learned how to threat model. Now I only do system encryption on my Laptop and encrypt internal and removable storage only. In the astronomically unlikely event the feds kick down my door for downloading Linux ISOs, I just hit the power button on my rig and the drives are scrambled. As a bonus, my
HISTFILEs areunsetso history is lost at every logout or any other session restart. Oh, and.bash_logoutis set to do ahistory -c, just in case.This guy doesn’t like
^rNot across sessions, no :D
Do you have dotfiles for that somewhere on the internet?
What’s a dotfile? 🫣
Edit: I see. I don’t. Open your
.bashrc(or/etc/profileif you want the settings to apply to all users) with your favorite text editor and addunset HISTFILEto disable automatic saving of command history. Similarly, addhistory -cto.bash_logout(or to/etc/bash.bash_logoutfor system wide). Reboot or logout/login orsourcethe above files to apply immediately.A dotfile is your next rabbit hole!
You know that dotfiles (files that begin with a dot) like
.zshrcor.bash_logoutcan contain important scripts or configuration for your system(s). Same with all the configuration files that can be scattered in directories like.config/or.gnome/.The “modern” dotfile means a configuration file that has been saved somewhere so that you can make a backup, or have the same dotfiles on all your machines.
It’s usually saved in git and on GitHub, but crazy people have written whole applications to handle those files (https://wiki.archlinux.org/title/Dotfiles#Tools). I like chezmoi, written in Go, but you have others like
stowfor example. Those applications handle diffs (when a file has been changed, you see the diff, you can save it or reset it), templates, multiple machines, upload to git, etc. Some applications use a hidden git repository for your files, others use hard-links. Last but not least, you can say “here are the files for Windows, and others files for Linux” if you have different machines.At my last job I stored on GitLab all the ZSH configuration files, CLI applications configuration, and even macOS configuration files that were in my HOME directory. If my machine ever crashed, I would have been able to restore it in a few minutes thanks to chezmoi, like: format computer, install chezmoi and git, reapply all the dotfiles as if nothing happened.
If you want examples of what can be done, a lot of people store theirs on GitHub: https://github.com/search?q=dotfiles&type=repositories
And this: https://github.com/webpro/awesome-dotfiles
Jesus Christ 😅 I knew what they are, then, without knowing what they’re called. But what on earth is all this managing enthusiasm surrounding them?! 😅 Would one have a 100 versions of the same dotfile or what? Mind you I have three computers, manually manage a handful of dotfiles + having a backup of them. Please explain a scenario where I would need one of those honking management tools. 🥹
Practice, paranoia, obsession.
dealer’s choice
It looks like a fad, but when you use it once you can be hooked. I see this see as an additional step in automation and making sure your computer is properly set up.
Having the same files across all machines is nice, and it’s backed up. You don’t have to think about it every day, at most once a week to check if a file has been changed and not pushed to git.
Most of the time, you want to have the same .zshrc across all Linuxes and Macs. That’s where such a tool can be useful.
If it’s in a git repository, the latest commit (transparent if you use a tool) has your files. At most 20 unique files for me but all at the latest “git version.”
If you want to save your dotfiles on git, or if you want to have the same configuration on multiple Linux machines.
I don’t remember the commands but once a week I would do:
deleted by creator