Okay. Non-published repo? Really? That definitely make pCP an
outlier! :-) Good to know, though -- I'll stop looking. ;-)
My local mods aren't all that big. Mostly a few long-running scripts
that I start from "User command #1", which lives in /home/tce. I think
I also needed to have /ro
You cannot access our git project.
Using .filetool.list and .xfiletool.lst are a piCore standard.
Plus, adding some features *may* modify .filetool.sh
See "'piCorePlayer backup'
(https://docs.picoreplayer.org/information/pcp_backup/)".
Adding features to piCore is usually done through extensi
Got it. I'm on my own. ;-)
Thanks!
pgf's Profile: http://forums.slimdevices.com/member.php?userid=58510
View this thread: http://forums.slimdevices.com/showthread.php?t=114828
__
See "'piCorePlayer Releases'
(https://docs.picoreplayer.org/releases/)".
Although we test insitu-upgrades, its usually only from recent releases.
Because of the hundreds of variables, there are no guarantees.
>From time to time, we need to increase partition sizes or restructure
some aspect of
I've looked for .filetool.lst in git, but it's not jumping out at me,
and the fact that it and .xfiletool.lst are both dot-files makes me
think they must be created from some other list or tool.
In order to get few more things backed up (since they contain local
mods), I've added several lines t
A couple of questions, before I do my first in situ upgrade.
I assume that anything backed up (i.e., listed in /opt/.filetool.lst)
will survive the insitu upgrade, correct? Likewise, the modules
installed via onboot.lst?
I'm running 7.0.1. Is it okay to upgrade straight to 8.1, or do I need
t
