How to boot/install with extracted core.gz image ? Make boot Faster?

[Crunch3D]

Hi

I need tc for a project and it should boot really fast. Now the boot time is around 10-11 seconds. I have only one extension openssh. I dont need gui so i use text interface (i think this should boot faster than 10 seconds shouldnt it ?). I tried installing it with the tce installer onto a virtual hard disk (frugal mode) and it worked but boot takes that long. After some looking around i think this is because of two tings:

1. The system is not actually installed into the system instead its the core.gz and a squashfs filesystem wich needs to be extracted on boot. On top of that the extensions needs to be loaded.

2. Extension loading needs time.

What i want: An uncompressed system on the hdd  (like any other linux like arch etc)(size does not really matter here, i just need speed and low ram useage)

I know I can remaster the iso to include the openssh extension but how can i install the system really onto the hdd without the sqashfs extraction so it would boot faster ?

My goal is to boot it in 2-3 seconds to tty of tinycore. Is this doable ?

I already read some other threads here and added te boot flags and this helped. But the extraction of the os and the loading of the extension would at least shave of 3-4 secnds I belive.

How would you proceed to boot that fast, if that is even possible ?

Thanks for your help and time

[Juanito]

Which version of tinycore are you using and for which architecture?

Are you using tinycore in a vm and, if so, which one?

Note that tinycore loads the root filesystem into ram.

[Crunch3D]

Yes i try to install it in VMWARE Fusion.

TinyCore64  11.1 the newest one

Can i install it normaly to make it boot faster or are there other methods in booting faster. Would the x86 version help ?

Is the 3 second goal achivable to tty ?

Another thing is that searching for hardware takes like 1-2 seconds. How can i deactivate the search or givse some default answers. Im already using flopy=none, cdrom=none, sda2=none etc.... Any other command lines that would help speed that up ?

Thanks a lot for the support i appreciate it :-)

BTW: I used the Install in VMware guide in the wiki in addition to the install guide.

[Rich]

Hi Crunch3D
Welcome to the forum.

... 1. The system is not actually installed into the system instead its the core.gz and a squashfs filesystem wich needs to be extracted on boot. On top of that the extensions needs to be loaded. ...

This is by design. If something gets messed up or infected, rebooting will likely fix that since the file system gets rebuilt
from scratch from files containing read only file systems.

Be aware, attempting a fully persistent installation may (or may not) clash with some of the systems scripts:
1. /etc/init.d/               # Contains scripts used for booting.
2. /usr/bin/tce*           # Scripts for installing, removing,  and updating extensions.
3.              # Other scripts I haven't thought of.

Support may be very limited since Tinycore was never intended for this type of installation.

[Juanito]

If you don’t need a gui, CorePure64 will boot faster than TinyCorePure64.

[Crunch3D]

Hi Rich,

Well thats good to know. In the end, i dont need to make it a regualr install. It just needs to boot lightning fast.

I read on other threads that bootet it with X and firefox and stuff in 10 Seconds. So i think it should boot faster than that without X.

To achive this im here. How it is done is not so much a prioritiy for me.

Any Tipps ?
Thanks!

PS: Good to see that the forum is so active :-)

[Crunch3D]

If you don’t need a gui, CorePure64 will boot faster than TinyCorePure64.

I used tinycore to install it without gui. Is this the same than CorePure64 ? Does x86 boot faster than x64 ?

[Juanito]

Yes, without gui is the same as CorePure64.

I don’t notice a difference between booting 32-bit and 64-bit.

[Crunch3D]

Ok. Thanks, what is your boot time to Core ? Just to get me feeling if i can come under the 10 seconds or if this is not possible at all.

Thanks

And if you boot faster, please share how you do it :-)

[xor]

I studied the opening delay in depth.
The whole problem is that the file verification process takes a long time.

http://forum.tinycorelinux.net/index.php?topic=24364.msg154382#msg154382

[Juanito]

In some quick and dirty testing with CorePure64

* 2-3s base norestore with waitusb
* 7-8s loading 80 extensions, but no backup

both on a 5-year old laptop without vm

[Juanito]

..4-5s booting the CorePure64 iso with a qemu vm

[Crunch3D]

OK if i would remaster the iso with the stuff i need inside, i could use norestore to just boot the iso without the hard drive stuff correct ?

For the extensions i would have to extract them and put them into the /usr/local/ folder correct ?

7-8 seconds is rerally good. I need like 10 seconds for one extension.

Can we deavticate validation of tces at startup ?

[jazzbiker]

Hi, guys!

@Juanito
Sorry for the dummy question: does "waitusb" bootcode has some sense in virtual machines?

[Rich]

Hi Crunch3D
You can get a better view of where time is being spent If you add these boot codes:

Code: [Select]

printk.time=1 syslog
After the system comes up:

Code: [Select]

dmesg > dmesg.txt
If you look through  dmesg.txt  you will find all of the kernel events along with timing.

If you look through  /var/log/messages  you will see those same events interleaved with operations being performed by
various scripts. If  /var/log/messages  overflowed, the earlier stuff will be in  /var/log/messages.0.