- cross-posted to:
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- cross-posted to:
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
I honestly wouldn’t recommend this for any server, and probably not for a workstation. This is useful for learning but could easily be a nightmare when troubleshooting an issue on a remote machine.
It’s always a great idea to do updates when you can give them your attention. Even if it’s you triggering them via ansible or other automation.