So I’ve been watching with interest the doings around CentOS/ Rocky/Cloudlinux, and wondering…what would it take to build a server branch of EOS? I have mainly used Debian+Ubuntu for the servers I have built, and there have been issues still with dependency hell, out-of-date-ness for new hardware, etc.
Is it possible to fix a repo at -1month for instance? Or even configurable?
What other tools would be necessary for a corporate environment?
I have relied extensively on Webmin in the past for the *Deb distros, and it has limited functionality for Arch, so what else might there be? A central point for system admins is vital IMNSHO, particularly where Samba/AD is concerned.
Yes, but I am think of “unrolling”, that is to slow down the update process hugely, and have it curated, so the parts that are being updated are being tested against all the common security flaws and hardware failings, in order to provide that stability and security, with the benefits of the speed in the Arch + pacman system. Yes it would be a huge undertaking, and require more $$$ than I have ever seen, but I was merely wondering about the technical feasibility.
And yes, @ricklinux, this would then be very similar to Debian, except based on the pacman system, and from my experience therefore less prone to breakage, with a more modern hardware handling.
How about a cheap(er) way - run a tester server separately, and keep the mirrorlist on the ‘real’ server a month behind running on the archives? Just sed the date for a month back, and run -Syyuu daily - and always have a month’s warning of trouble ahead.
OK - I only ran Netware when I needed servers - so I am probably out to lunch
It’s also an outdated guide - this was written back when the base package was still a group that included the kernel (and a few other little goodies like network management software, a text editor…). Follow this guide and you won’t have a kernel installed.
As always, one should refer to the Arch Wiki, as it is the most up-to-date installation guide for Arch.