I see that the 'patcher' is talked about in a couple threads lately, but there is very little information about it that I can find from a search.

I see that LivePatch.sh was introduced in R5F1 (changelog) and I understand that it runs itself upon install. But I was looking for more information. So to those who might be able to assist:

I see that there is a 'list' of patches that it makes (The F27 Hint thread). Is this list public? Should the patcher be run from time to time to update what wasn't available at the time of install? If so, maybe a crontab for once a month? Would that all hit the KM servers too hard?

I really like the idea of a LivePatch that can make needed updates in a timely fashion. I was just looking for a bit of a discussion on it.

TIA

My understanding of the patcher is that it is only run at install as it is to address issues that have been identified on a standard system. The problem with running it after a system is installed is that there are too many things that could have changed over that time and thus would not be practical to run it on an installed system.

_________________
Girkers

Well the ability to run the patcher only at install does limit it's versatility a bit. It makes it more hit and miss with what was updated due to the day/time that you installed. (ie a F27 install on 9/11 could be far different then a F27 install on 9/22.) And maybe the most puzzling part would be that the differences would be unknown. Perhaps publicly tracking additions to the patcher publicly would ease troubleshooting?

Another 'gotcha' with a run-once internet based patcher is that if your net connection is down for whatever reason, your not getting the latest fixes.

(Just a few observations, not meant as criticism.)