Quote:
Originally Posted by NiMa
So if I'm right, I should edit /etc/inittab with the loop0 thing (do you have an example?
|
You should most definitely *not* do that, as the inittab may be overwritten by a FW update
.
The loop0 thing relies on custom udev rules instead to avoid that. (c.f.,
https://www.mobileread.com/forums/sh...p0#post4092742).
Quote:
Originally Posted by NiMa
Do you do some sort of "signing" in your packages? That could help the script decide if it has to update KFMon or not.
|
Not really. Assuming KFMon is up, you can query the current version via
echo "version" | kfmon-ipc 2>/dev/null.
Keep in mind that the OCP ships a rolling release build, so expect getting a git-describe version scheme (e.g.,
KFMon v1.4.3-18-g1b586a5).
If that helps, remind me to push said build during the OCP upload, that way you have a chance to actually download binaries without jumping through extra hoops
.
EDIT: Done. It's listed in the
HTML index, and I added a
JSON manifest like the KoboStuff packages.