integrate extension into filesystem ?

[halma]

Hi,
i am asking myself if it possible to ingrate all needed extensions(incl. dep's) of my needs in the filesystem "core.gz" (like Picore 9.x) to skip the extension loading on boot, may it can accelerate the bootprocess ?

[Misalf]

No/Yes.

If you pack all the stuff you need into the initrd (core.gz), the boot loader has to handle it. Depending on the size of the resulting initrd, it might fail/succeed to boot depending on size, which boot loader and/or hardware is used.
I learned that a >100MB initrd works on some systems but not on all. For older systems and simpler boot loaders it's a miss most of the time.
There is a benefit in putting stuff into the initrd but I wasn't able to find a sweet spot. And I prolly won't continue searching.
The compromise I found most reliable was to merge OnBoot-extensions into one big bloated extension. Less duplicated work and way less mounts but more user intervention required in case of updates.

Script posted here:
http://forum.tinycorelinux.net/index.php/topic,20709.msg129945.html#msg129945

[core-user]

I only put what I need immediately 'on boot', others I put 'on demand', that may help in your situation

[Rich]

Hi halma

Hi,
i am asking myself if it possible to ingrate all needed extensions(incl. dep's) of my needs in the filesystem "core.gz" (like Picore 9.x) to skip the extension loading on boot, may it can accelerate the bootprocess ?

That does not skip extension loading. It just changes the manner in which they are loaded. Instead of mounting extensions and
symlinking the contents into the RAM file system, you will wind up copying the entire contents of the extension into RAM file system.
So now your extensions will all be using up RAM regardless of whether the programs they contain are running or not.