Dave - all the best with ClearOS, hope things work out for all at ClearOS and its users. I see steps are starting to be taken in the right direction but has been rather slow coming. For me this is the parting of the ways as I hinted before, ClearOS 7.6 will be my last version before moving to a more stable platform As a retired person on a fixed income there is no way I am going to pay for Home or Business Editions for the number of systems I control. It's been fun at times - frustrating at others. Good luck.
I am still learning this side of things
Started using ClarkConnect about 1998 and no idea how long it had being in operation before that. Are you saying that in all that 21 years or more no written procedures have been created, and kept updated, for essential tasks within the company? Each new person learns by trial and error? Nothing passed on from one person to the next so every change in personnel results in being back to almost square one Not your problem per se. "Seat of the pants" culture? Hope none are pilots
Brings to mind this aphorism from George Santayana (1905) Reason in Common Sense, p. 284, volume 1 of The Life of Reason
"Those who cannot remember the past are condemned to repeat it"
When in a former life I worked in IT/Company Change Management-Control - that was one of our mottos... The same is true for those unaware of the past. The problem you mentioned re. rpm updates syncing to repositories has been well known for many many years - so why should it still be a recurring problem... Other distributions I use mitigate it pretty well... Cannot remember the last time it happened to me with Ubuntu/CentOS/Fedora (just a sample of one person I realize).
Anyway - this is now OT - sorry.
Thanks Nick - will try again tomorrow...
However, does the present process really rely on casual conversation between staff and one's memory? If so, that's a recipe for continuing problems. Surely there should be a written procedure whereby numerous checks are made before making an update/addition to a repository, e.g. dependencies are met. Also a test install conducted to confirm the updates will not cause issues. From an outsider looking in it gives the appearance it's a rather haphazard modus operandi at best with no change management/control. It certainly doesn't engender confidence in the product.
Updated two machines with the latest 7.6 updates as of Wed Apr 17 16:20:00 AEST 2019 (Sydney Local) including kernel 3.10.0-957.10.1.v7.x86_64.
Both rebooted OK and running OK (All CPUS running at 100% 24/7 courtesy of BOINC and medical research from WCG - so some stress testing...)
These are the two machines, the test machine will be powered off if no problems over next 24 hrs...
Thanks - Ah OK - misunderstood the date "Community Report - 2019-04-13" - didn't notice the post was just a few hours after the published time of day for the meeting...
My question still stands - where will the minutes be posted?
Dave - where is this, or where will it be when written?
Start weekly report out of status for those not at the meeting
Had a quick look on both gihub and docs.clearos.com - couldn't see it... Actually, Not really sure where to look...