just for some background this is what the config file for the script currently looks like.
less -N CompileResizerYou can navigate with the PageUp, PageDown, up arrow, and down arrow keys.
-------------------------------------------------------------------------------------------------------
Line:
__3 I alias to busybox commands when possible since they are always present and because the GNU counterparts
sometimes behave differently. I also set options to the commands there.
_28 Sets the compiler flags to match the processor you are currently running on.
_65 to _79 I don't use make files for stuff I write so the compile and link commands go here. The size and
ls commands give me an indication of how big my program is getting as I develop it.
You would replace this with:
export CFLAGS CXXFLAGS LDFLAGS PREFIX DESTDIR plus any other variables you need to export.
./configure --prefix=$PREFIX
make
make install
_81 Uncomment this line to exit the script early if you are getting build errors. Re-comment it once the
errors have been resolved and rerun the script.
_94 The build results are archived in a separate subdirectory for each processor type. This way you can
use a removable drive to build on different architectures while retaining a backup of the other builds.
117 This is where the .info file is created. Most of the variable fields get updated automatically. The
Change-log: field (line 188) needs to be updated manually when new versions are created.
-------------------------------------------------------------------------------------------------------
If there can be a standard file designation created for this situation for permanent storage that would be great as this will assist in creating scripts on the fly etc... such as in tce.installed script.
Some programs when you run them will automatically create configuration files under the users ~/.config directory, such
as geany, gpicview, libreoffice, mc, wireshark, etc. Some will create hidden directories directly in the users
home directory, such as claws-mail, dillo, fifth, mozilla (Firefox), ssh, etc.
Some extensions conditionally create config directories/files through their tce.installed script, such as bash, grabber
and gtk3.
If you boot an ISO, there is no persistence, and I don't think a backup option is available either.
If Tinycore is installed, /home and /opt are backed up when you use the Exit icon.
If Tinycore is installed, and you have persistent /home and/or /opt directories, those directories should not be backed up.
... Please note the file is from win .txt (notepad utf-8) and has end of line characters, still need to figure out how to correct this any help appreciated :)Try this:
dos2unix buid.cfgmkdir -p pkg/usr/local/binmkdir -p pkg/usr/local/etc/haproxyIt then gets packaged using squashfs-tools.tcz:mksquashfs pkg haproxy.tcz -noappendWhen tce-load installs the extension, it mounts it under /tmp/tcloop/ and links the files to the /usr/local file system.pkg/usr/local/etc/haproxy/haproxy.cfgIf the location of the .cfg is hardcoded to /etc, have the tce.installed script create a link to /usr/local/etc/haproxy.sudo busybox cp /usr/local/etc/haproxy/haproxy.cfg /usr/local/etc/haproxy/Then make their changes, add usr/local/etc/haproxy/haproxy.cfg to /opt/.filetool.lst , and run a backup.... When there is a change made to the .cfg, run the backup (this means a backup must be run on exit otherwise the .cfg changes will be lost). ...Use the ControlPanel to call up the Backup/Restore application.
... The /opt/ files can be altered (but presumably not advised to do so) as a backup/restore will be performed on those files in mydata.tgz? ...If something needs to be altered in /opt/ , that should be mentioned in the Comments: section of the .info file.
... If the pc is rebooted say by power outage it must have an automated login ...The default user is tc and is logged in automatically when booting.
... (and Onboot entry) else the software is not started (or can a tce-load be done before login ?) and there will be no script as ~/.config will not be created. ...When the system boots, It checks the tce directory for onboot.lst and loads all of the extensions listed in there. It
... Just a little note, there is no .config file in RPi-64 13.0.0 on a clean install is this an oversite or is the ~/.config being phased out?I don't think that directory gets created until something actually needs it.
Typically what you would do is place a default configuration file in:
Code: [Select]
pkg/usr/local/etc/haproxy/haproxy.cfg
If the location of the .cfg is hardcoded to /etc, have the tce.installed script create a link to /usr/local/etc/haproxy.
If the end user wants to customize the .cfg file, they can make it editable by:
Code: [Select]
sudo busybox cp /usr/local/etc/haproxy/haproxy.cfg /usr/local/etc/haproxy/
Then make their changes, add /usr/local/etc/haproxy/haproxy.cfg to /opt/filetool.lst , and run a backup.
Thank you very much for your feedback, ...You are welcome.
Typically what you would do is place a default configuration file in:Correction, that should have said:
----- SNIP -----
add /usr/local/etc/haproxy/haproxy.cfg to /opt/filetool.lst , and run a backup.
... Also just noticed you have different area for scripting in the forum so sorry for raising it here ...Since this was less of a scripting issue and more of a "How Tinycore works" issue I think it is fine over here.