Tiny Core Base > TCB Talk

Boot times of various OSes on EeePC 901. How does TC stack up?

<< < (2/3) > >>

roberts:
I would venture to guess that you are comparing TC to  traditionally  hard drive installed systems.

You don't state which of many modes of operation that you are using (see Getting Started).
TC's design goal is to be nomadic and not a traditionally installed OS. 

Not only are these other modes of operation available but many other "tuning options" including.

1. Using the optional/ directory
2. PPI mode, i.e., tclocal,( persistent /usr/local/) where all extensions are "installed" and not loading upon each boot.
3. Persistent /home.
4. Persistent /opt

Any combination of the above, as well as combining extension into a personal "collection" as per Jason's post.
I had been suggesting that we offer "collections" but that would mean even more effort to update.

If you wish  booting to a pristine state, being nomadic is not important, you can use any combination of the above to completely eliminate the backup/restore requirement and loading upon boot.

You can, as some have already, perform a "traditional hard drive installation".

So really, to be fair, TC should be listed at a minimum of 5 times showing boot times for all the capabilities and choices that TC supports and allows.

Jason W:
A good method of running TC to achieve quick boot times would be PPI with persistent home.  I shouldn't be recommending experimenting with unsupported modes like combining extensions as it can create problems.  Breaking the extension system and dependency logic is not worth shaving a few seconds off boot time.

paulfxh:
Thank you for the replies.
Right now, I'm using the PPR/TCE operating mode in TC 1.0.
From your comments, and having read again the Getting Started page, it seems that the fastest boot times are likely with the PPI/TCE mode.
Right now, I have a folder called "tce" in /mnt/hdd7 and I use a bootcode on the kernel line of "tce=hdd7".
Can I assume that I can switch this to the PPI/TCE mode simply by replacing the "tce=hdd7" bootcode with "tclocal=hdd7" and by creating another folder on /mnt/hdd7 called "tclocal" to which I will transfer all my tce extensions?
Just for information, the java.tce takes about 20 seconds to load on my EeePC 901. Everything else is considerably faster to load although opera.tce, compiletc.tce and linux-headers-2.6.26.tce each take around 10 seconds to load. So just these four extensions account for more than half of the loading time of the total of 24 extensions.

^thehatsrule^:
iirc there was a mistake spotted, and that the actual bootcode should be "local=".  Also, I think that since you already were using tce=, you might be able to quickly set up tclocal by using "tce= local=" after creating the tclocal dir once and then use "local=" on subsequent boots.

Note that some things outside of /usr/local may have to be manually backed/restored, or it may be easier to remain as extensions.  For example, I think compiletc is mostly not in /usr/local, so that should be left as an extension.  Although, if you typically don't use the dev tools, loading it only when needed may be better?

cjgau:
Hi Paul, Just for reference, I've been using/playing PPI/TCE --- SD card on Asus901, IDE-CF on miniITX (John's toy), and CD on Dell 4550; the TC's booting is much faster than DSL 4.4.2

As to Haiku and Senryu, do you run them by VMplayer? or HD installed?

Navigation

[0] Message Index

[#] Next page

[*] Previous page