Removed by mod

Consider PCLinuxOS. ‘PLOS’ has the same look and feel of the ent Linuxes, but

• as a child of mageia/mandriva from mandrake and conectiva, it’s derivation from RH is super long ago so it’s closer to rhel5 for well-built well-tested tools.

• it has maaaaassive lib/app support range, like Axel Rose’s vocal range compared to EL’s Bruce Springsteen. No stream or other crap shenanigans aside from etc/alternatives.

• No systemd. Weird how startups are fast and reliable

It can yum cron like a badass.

Caveats:

• if you liked building vagrants on mageia, you need to help them on pclos. They have no clue there, and the skillet seems to be fading fast.
• people who support sysv startup are getting more lazy and ditching it.
• people who support last week’s version of anything are no more prevalent in pclos, so there’s no magical fix for “10 second tom” devs here either.

I think some of my units are on the ‘lgtm’ update plan too. ;-)

I’m aware I’m jinxing myself when I suggest that I’ve had very different experience. We’re mostly WDReds though.

There’s a lot of value in a sleeping area that can get really really dark.

I’m ever so grateful for electrical tape.

It’s a signed archive of deployable files along with meta-data. Usually a cpio archive (which is similar to a tarball) with that extra signature wrapper and meta-data (which, itself, should be a list of files and checksums).

A proper package can validate a project’s installation, either from the local database or from remote resources, at any time, which gives positive assurance that what is installed is what should be installed.

As well, proper package info is exported by SNMP to be consolidated centrally and validate what is vs what should be installed at the group level.

TL;DR? Like a tarball with tracking info, signatures, checksums, and top-to-bottom validation. If it’s a good package, anyway.