question about extensions

[P5music]

Hello,
I ask what happens when an extension is loaded, as with tce-load. I would like to know what changes on tinycore system, for example: "this is mounted there", "this file is updated", "this directory is created" etc.
I hope it is not so complex that this question cannot be answered here.
Thanks

[tinypoodle]

Code: [Select]

less /usr/bin/tce-load

[Juanito]

The extension is mounted as a loop device /tmp/tcloop/extension_name.

Symlinks are created in the tc base filesystem for each file in /tmp/tcloop/extension_name as:

/path-to-file/filename -> /tmp/tcloop/extension_name/path-to-file/filename

[P5music]

so,
just mounting and symlinking are performed?
no other file or register is updated?

[Juanito]

There's more to it than that - have a look at the tce-load script as suggested above

[P5music]

I looked at the script and it seems that much work is done every time.
Is it possible to choose a bunch of extension that serve for a particular purpose and create a tinycore systems that just mounts and symlinks, without all that work?

I explain:
I experimented and found useful, for a particular purpose, symlinking /root to a permanent directory, putting a symlink creation command in .xsession (after a rm command that deletes the original /root stuff). It works. So I think this method could be useful also for creating a non-standard tinycore system in which I put in .xsession some commands to connect the extensions stuff to persistent directories created only the first time (copied from RAM "filesystem" if the stuff is there).
I know this sounds like making a customized linux system but I want to use tinycore because it is a good starting point.

[gerald_clark]

/root is not the root file system.

[maro]

In case you want to find out exactly what commands are executed by 'tce-load' why don't you run it like sh -vx tce-load -wi EXT That should give you a fairly good idea.

Please note that any scripts that are called in that process will run "outside" of the '-vx' scope. But if that is the case and you really want to know what's going on you could create a custom version of 'tce-load' where you replace 'SCRIPT-NAME OPTIONS' with 'sh -vx /path/to/SCRIPT-NAME OPTIONS'

I'd suggest you do a bit more of your own work instead of asking that many questions you could find out easily by yourself by studing the relevant code properly.

[P5music]

@gerald_clark:
OK it's not root filesystem but I made /root persistent and it served me very well.

@maro
I thank you all for your patience. Yes I realized it is better to study and search on my own. Indeed I am studying LFS book, but I am struggling as far as I can not to have to do all that work because many things some people said I could not do with tinycore, well, I am doing them now. I am sorry that when I "touch" certain subjects no real information leak, so I think I'd better hurry up reading that book.