On 2023-08-24 18:30:14 (+0200), Christian Heusel wrote:
On 23/08/24 09:05AM, Pascal Bryner wrote:
The reason for this request is: We're running 60+ Arch clients for our employees (tendency increasing), which all are managed through a central application, where we can execute OS-updates, software-installs, firmware-updates, etc.
The main problem is, that if we execute a company-wide update, some people directly install them and some postpone them as far as possible, sometimes taking vacation without installing the updates first.
This leads us to the problem that the clients don't have the same state, sometimes with a 2 week or more gap, which makes it difficult for us to troubleshoot any problems.
To add an additional datapoint to this: You might want to have a look at an image based update scenario for your clients, using systemd-sysupdate [1] etc.
So as you might have already guessed I am a bit sceptical regarding your idea(s) but also very interested in your reasons/motivation.
I can only 2nd this. From my (admittedly limited) perspective it might be more beneficial to work with an unmodified Arch Linux and only provide certain packages in an additional repository (in case you need something outside the scope of the official repositories). An image-based update scenario would then significantly cut down on the diversity of states a client system might be in. If you do anything like that and are able to share your experience I (and most likely all of us) would be very interested! Best, David [1] https://man.archlinux.org/man/systemd-sysupdate.8 -- https://sleepmap.de