Can TC not put home,opt and tce folder in any place?

[BALLOON a.k.a. Fu-sen.]

I have one dissatisfaction in TC.
TC monopolizes one partition at small capacity.

When we want to put TC of the different version of the return number,
we must distribute a partition.

Latest Puppy Linux put one folder in a partition.
We can in this way establish different Puppy of the return number to one partition.
I think whether the same thing cannot be realized in TC.

[Misalf]

In Puppy, the puppysave.sfs file contains /opt and /home.
In Core, it's the mydata.tgz file but it works differently; repacking some hundred MB on shutdown would be just crazy.

You can, however, specify an exact path for the  /tce  directory via bootcode:

Code: [Select]

tce=/boot/TinyCore5.x/tce
Or even for a specific drive:

Code: [Select]

tce=LABEL="MyHDDLabel/boot/TinyCore5.x/tce"
Also via UUID instead of drive label:

Code: [Select]

tce=UUID="12345678-90ab-cdef-1234-567890abcdef/boot/TinyCore5.x/tce"
Unfortunately, this doesn't work for /home and /opt.

EDIT: I've added quotation marks in the 'code' like I have it in my bootloader.

[coreplayer2]

AFAIK boot codes allow you to place home, opt and tce directories on any partition you desire, making tc extremely flexible.

My typical configuration below is an example.   Here i have installed the boot files on sdb4 (different versions of core, corepure64, vmlinuz, grub etc etc., in this case I boot from either core or corepure64).   While tce, home and opt directories are located on partition sdb3 within their respective x86 or x86_64 directories, the home directory is shared between both core and corepure64 installations.  opt and home is removed from filetool backup.  Where specific files conflict between installs then those alone are backed up & restored using filetool's mydata.tgz from within their respective install.   

[Lee]

I think he wants to put them in arbitrary subdirectories on a given partition as is done with the tce directory.  AFAIK, that's not implemented yet in Core (I'm still on 4.7.7).

I went to look in to what would be involved, thinking perhaps it would be easy to borrow the logic from the handling of the tce boot code, ... and was unable to find where in /etc/init.d/tc-config the tce boot code is processed.  I don't have time to give it my undivided attention right now, but will check further later.

[Misalf]

Yes, /tce, /opt and /home can be placed at different partitions but only /tce can be placed in a sub-directory.

I don't know if there are any technical limitations for  /opt   and  /home  not being able to be defined to be located in sub directories. Would be nice.
I have as well tryed to define specific locations for  /opt   and  /home  to be on my 'Linux' partition where another distro was installed and things got a little messy. No problem for  /home/tc  but for the files I had in  /opt , I didn't really know from which distro they came.

Currently I have several big files and folders moved out of my  /home/tc  folder and symlinked them back - So the backup is still small and fast.
(i.e.  /mnt/sda4/boot/TinyCore5.x/STUFF/.wine  ->  ~/.wine)

[coreplayer2]

H'mmmm, 
I think opt is small enough to keep in filetool.lst  for each booted tc version  no?

The OP doesn't appear to be clear on whether he needs to install in defined directories or defined partitions. Or both


Sent from my iPhone using Tapatalk

[Lee]

I would agree that /opt is small enough to keep in mydata.tgz ... in my case.  But someone who had something large in /opt or had an unusually pressing need to keep the back up -really- small might not find it so.

Also, some users might want to share personal data, but not, for instance, bootsync.sh and bootlocal.sh, among different machines.  I do that, although I devised a way to keep boot*.sh specific to each PC.

In addition to the likelihood that it would be really really useful to at least -some- users, it seems to me that just the logical symmetry of being able to handle /opt and /home the same as the tce directory would make it worth updating the opt and home bootcode logic - unless there is some practical reason why it couldn't or shouldn't be done ( as there was a good reason not have persistent /usr ).

[BALLOON a.k.a. Fu-sen.]

Wow!  Thank you for an everybody answer.
I did not think that many replyed so in a short time.
I seemed to ask a useful question.

tce boot code can do this expression, too:

Code: [Select]

tce=sda5/boot/TinyCore5.x/tce
This value (partition/dir) including here is effective in save or backup.

There is restore in boot option, but may you set this like tce, too?

[coreplayer2]

May I suggest reading the corebook http://tinycorelinux.net/~curaga/corebook.pdf