Ten years of the same Arch Linux installation
Summary
David Runge reports how the same Arch Linux installation survived several hardware and system changes over ten years. The Arch installation described had existed since 2012. It outlasted several hardware and storage migrations.
Ideas
- Rolling releases spread large version jumps over continuous maintenance.
- Regular full updates prevent unresolvable mixtures of packages.
- Configuration notices accompany changes that require manual work.
- An installation can be migrated to new disks and hardware.
- Documented customisations reduce your own operational complexity in the long term.
Insights
- Longevity comes from continuous maintenance, not from unchanged software.
- Small regular interventions can be superior to rarer large migrations.
- Your own configuration discipline often determines stability more than the release model.
Facts
- Arch publishes necessary manual interventions before problematic updates.
Recommendations
- Read the Arch news before larger updates and avoid partial system updates.
- Back up the package list, configuration and boot environment before hardware migrations.
References
Links to the original source and the Web Archive open in a new tab.