What I've actually found is that the command 'remaster.sh /path/to/ezremaster.cfg rebuild' re-runs everything that ezremaster itself did, which would be great if modifications to the /extract files hadn't been made by clicking on the blue links in the last page. The rebuild script does everything, including making the contents of the /extract directories, but it only knows what is in ezremaster.cfg, so any edits are lost. Is there are way to just build the system from the pre-existing /extract directories?
As an aside, I notice that the script only seems to work after ezremaster itself has at least been started. Is this to be expected?
Is there an answer for this, or do I have to re-run ezremaster every time?
If what you are trying to do is automate rebuilding your remaster that includes custom changes made within the filessytem, I would recommend this approach:
Create your ezremaster.cfg file. Then create a script such as the one below that you can use to automate rebuilding (for example when new versions of Tiny Core are released)
remaster.sh /path/to/ezremaster.cfg extractimage
remaster.sh /path/to/ezremaster.cfg bootcode
remaster.sh /path/to/ezremaster.cfg apps
<put your custom commands here such as copying in files, editing files, etc.>
remaster.sh /path/to/ezremaster.cfg package
When you run this, it will do all of the normal ezremaster stuff, and you can run any custom commands you want to customize the ISO contents or the tinycore.gz initrd.
This script could then be run any time a new version of Tiny Core is released to update your remaster.