# Tyblog | Industrial Strength Arch Linux

**URL:** https://forum.tjll.net/t/tyblog-industrial-strength-arch-linux/235
**Category:** uncategorized
**Created:** [September 26, 2020, 11:52pm UTC](https://forum.tjll.net/t/tyblog-industrial-strength-arch-linux/235 "2020-09-26T23:52:51Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![tyler](https://forum.tjll.net/letter_avatar_proxy/v4/letter/t/35a633/32.png) [@tyler](https://forum.tjll.net/u/tyler)
#### Post date: [September 26, 2020, 11:52pm UTC](https://forum.tjll.net/t/tyblog-industrial-strength-arch-linux/235/1 "2020-09-26T23:52:51Z")

</div>

These days, I _almost_ exclusively run Arch Linux in my homelab and personal machines. Had I the brain cells to spare, I’d try and get NixOS running on ARMv7, but in the meantime, a mix of vanilla x86\_64 Arch and Arch Linux ARM is my chosen flavor just to keep things consistent. I’ve run Arch as my primary server OS for almost a decade now, and although I’m sure some will balk at the idea, I’ve found that the distribution has performed wonderfully for me, even in contrast to traditional “server” distributions like CentOS. It sounds counterinuitive, but the simple model of Arch Linux has, overall, helped mitigate some maintenance burdens.

* * *
This is a companion discussion topic for the original entry at [https://blog.tjll.net/industrial-strength-arch-linux/](https://blog.tjll.net/industrial-strength-arch-linux/)

---

<div class="post-metadata">

### Author: ![brettinternet](https://forum.tjll.net/user_avatar/forum.tjll.net/brettinternet/32/66_2.png) [@brettinternet](https://forum.tjll.net/u/brettinternet)
#### Post date: [September 28, 2020, 3:58pm UTC](https://forum.tjll.net/t/tyblog-industrial-strength-arch-linux/235/2 "2020-09-28T15:58:35Z")

</div>

Great suggestions, I’m excited to try some of these out.

How often do you touch your Arch servers, or how often are you pushing updates? What’s the longest you’ve gone without running updates and what does it look like coming back to it? I also assume you’re running the LTS kernel?

---

<div class="post-metadata">

### Author: ![tylerjl](https://forum.tjll.net/user_avatar/forum.tjll.net/tylerjl/32/21_2.png) [@tylerjl](https://forum.tjll.net/u/tylerjl)
#### Post date: [September 29, 2020, 4:08am UTC](https://forum.tjll.net/t/tyblog-industrial-strength-arch-linux/235/3 "2020-09-29T04:08:57Z")

</div>

> How often do you touch your Arch servers, or how often are you pushing updates?

I work on some of the busier servers at least every other day or so (like my single x86\_64 machine), and when it comes to upgrades, I stagger an OS upgrade across my whole “fleet” about every two months. Since I usually can’t perform an upgrade across all the hosts in a single day (there’s 20 machines to work through), I usually precede the upgrade by doing a `pacmatic -Syuw` across _all_ the machines to prepare consistent downloaded package versions on each machine, then do `pacmatic -Su` on the hosts serially which might take a couple of days. I do this primarily because there have been times when running sync (`-Syu`) gradually over a few days has caused drift in package versions.

> What’s the longest you’ve gone without running updates and what does it look like coming back to it?

I’d say maybe six months has been the longest? Running a system update after that period of time isn’t very painful - I read upstream release notes via `pacmatic`, the actionable items which are usually some required `--overwrite` flags for certain packages, check the important parts after an update (primarily `dkms status`), and check `systemctl --failed` after a reboot to ensure everything has started up correctly.

> I also assume you’re running the LTS kernel?

I’ve kind of hopped between LTS and the mainline kernel. I’ve actually found that the primary differentiator between mainline and LTS to be the locked-in minor version - the patch version on Arch LTS kernel packages increments almost as often as the main kernel package does, so kernel package change cadence tends to be the same between the two.

---

<div class="post-metadata">

### Author: ![rhysperry111](https://forum.tjll.net/letter_avatar_proxy/v4/letter/r/a5b964/32.png) [@rhysperry111](https://forum.tjll.net/u/rhysperry111)
#### Post date: [October 3, 2020, 9:00pm UTC](https://forum.tjll.net/t/tyblog-industrial-strength-arch-linux/235/4 "2020-10-03T21:00:27Z")

</div>

Just so you know, you put `sudo system edit darkhttpd` in one of your examples. I’m pretty sure you mean `sudo systemctl edit darkhttpd`

---

<div class="post-metadata">

### Author: ![tylerjl](https://forum.tjll.net/user_avatar/forum.tjll.net/tylerjl/32/21_2.png) [@tylerjl](https://forum.tjll.net/u/tylerjl)
#### Post date: [October 4, 2020, 1:34am UTC](https://forum.tjll.net/t/tyblog-industrial-strength-arch-linux/235/5 "2020-10-04T01:34:04Z")

</div>

I appreciate you catching that error @rhysperry111, I’ve updated the post and attributed you 👍
