what is the best practice for easy update & dist-upgrade:This is mostly irrelevant.
1. in terms of speed and easy of distro updates, it makes sense to separate
* /root (software (programs) that can be re-downloaded) (on
separate single suepr fast SSD or NVMe)
* /home (non-reblacable unique data (massive amounts of space with
8x4TB software mdadm RAID10))
2. when a new Debian 12 is coming outJust don't reinstall. Debian recommends using apt and following the
* how to re-play all those changes, installs, configs and programs
made to /root?
3. if things go wrong there is still this nice "show me all changes to(doesn't look like *changes* to logs for me, but whatever works for you)
logs in beautiful colors" one liner
* (ccze is very much needed also in Debian 12 :) (tried many
alternatives)
* find /var/log/* -type f \( -name "*" \) ! -path '*.gz*' -exec
tail -n0 -f "$file" {} + | ccze
1. install a very basic Debian 11 templateThis is over-engineering, unless you are going for the "infrastructure as
2. apply all changes (all changes will be recorded to a separate
partition (!?) or a local git repo!?) and saved as a "config
snapshot" that can be re applied as soon as Debian 12 template is
released :)?
On Wed, Oct 06, 2021 at 12:03:16PM +0200, dude wrote:
what is the best practice for easy update & dist-upgrade:This is mostly irrelevant.
1. in terms of speed and easy of distro updates, it makes sense to separate >> * /root (software (programs) that can be re-downloaded) (on
separate single suepr fast SSD or NVMe)
* /home (non-reblacable unique data (massive amounts of space with
8x4TB software mdadm RAID10))
Also "non-reblacable unique data" exists outside /home too, e.g. in /etc
and /var.
2. when a new Debian 12 is coming outJust don't reinstall. Debian recommends using apt and following the
* how to re-play all those changes, installs, configs and programs
made to /root?
release notes to upgrade to the next version.
3. if things go wrong there is still this nice "show me all changes to(doesn't look like *changes* to logs for me, but whatever works for you)
logs in beautiful colors" one liner
* (ccze is very much needed also in Debian 12 :) (tried many
alternatives)
* find /var/log/* -type f \( -name "*" \) ! -path '*.gz*' -exec
tail -n0 -f "$file" {} + | ccze
1. install a very basic Debian 11 templateThis is over-engineering, unless you are going for the "infrastructure as code" paradigm from the beginning (which is over-engineering for many
2. apply all changes (all changes will be recorded to a separate
partition (!?) or a local git repo!?) and saved as a "config
snapshot" that can be re applied as soon as Debian 12 template is
released :)?
use cases as well).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 240:44:27 |
Calls: | 6,624 |
Files: | 12,173 |
Messages: | 5,320,078 |