this post was submitted on 13 Mar 2026
4 points (83.3% liked)
Arch Linux
9601 readers
1 users here now
The beloved lightweight distro
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ok, so a few things to pick apart there...
If you're using
reflectorto find the fastest mirror, personally, I'd do that once and maybe check it... twice a year? As long as you have, say 3~5 mirrors, then if your fastest failed, you'll still update. And the 2nd / 3rd fastest are not going to be much slower.So, really, that could be done manually
But, that beings me on to ~.pacnew` in general. Again, IMHO, that should not be automated.
Ok, maybe
locale.genupdates can be ignored, but sometimes a config file really changes a lot. And that new file should be in your ansible master files to copy to all relevant devices.Handling different processor types? Not really a problem. If you have a load of devices then grouping your ansible hosts by OS type might be a good idea because they'll probably be doing similar things, but you're usually installing packages by name, doing an update, etc not OS specific usually...
You'll need SSH for a remote Ansible controller to access the devices, but using private key pairs, possibly only enabling on specific IP addresses, etc, would help.
Gotcha. That gives me are ideas. I think I'll put the Ansible controller / log machine on a VLAN and put the user functions in a LAN just to separate. Never done the VLAN thing so that will be interesting.