tce directory in home/tc - any problems?

[bigpcman]

Probably another bad idea but I was wondering what would happen if the tce directory was in /home/tc and /home was in the backup file. What would the "tce=" boot code be?

The idea being very simple portability for extensions.

[roberts]

Repeated backing up of static content is a waste of time.
The length of time to perform such is even more so.
The point of separate directories is the separation of static content versus dynamic.

[bigpcman]

Repeated backing up of static content is a waste of time.
The length of time to perform such is even more so.
The point of separate directories is the separation of static content versus dynamic.

Yes of course you are right, but I was just contemplating the situation where there are just a few small extensions present. My question is one of curiosity more than anything else to better understand how tc works.  Are you indirectly saying this is not possible?

[mikshaw]

The restore occurs after extensions are loaded, so I'm assuming it would not work.  It will work if you have a persistent home, but in that case you probably wouldn't have home in your backup anyway.

[bigpcman]

The restore occurs after extensions are loaded, so I'm assuming it would not work.  It will work if you have a persistent home, but in that case you probably wouldn't have home in your backup anyway.

OK, that's a good point. So I guess if the restore loaded a new bootlocal.sh file that executed a script like jpeters suggested in http://forum.tinycorelinux.net/index.php?topic=3062.msg15769#msg15769 with the appropriate tce-install commands (executed by the tc user) then the extensions would be installed from /home/tc. But that forgoes all the wonderful tc automation.