piCore-8.1.5 released

[bmarkus]

Team Tiny Core is pleased to announce the immediate availability of piCore-8.1.5 Changes:

* util-linux updated to 2.29.1
* fixed permission issues on /usr/local/tce.installed and /etc/sysconfig/backup_device

Download location:

http://tinycorelinux.net/8.x/armv6/releases/RPi/

There is only one SD card image, it supports all armv6 and armv7 RPi boards!

Please read README and don't forget to expand mmcblk0p2 partition according to your needs to make room for persistent data and installed applications.

If you need the basic TC GUI, install TC.tcz from the repository.

For support visit http://forum.tinycorelinux.net/index.php/board,57.0.html

[Misalf]

Wrong version string in
http://tinycorelinux.net/latest-armv6
http://tinycorelinux.net/latest-armv7

Code: [Select]

Warning:
You are running version 1.8.5
The latest release is 1.8.3


[bmarkus]

Wrong version string in
http://tinycorelinux.net/latest-armv6
http://tinycorelinux.net/latest-armv7

Code: [Select]

Warning:
You are running version 1.8.5
The latest release is 1.8.3


Thanks for reporting, fixed.

[Misalf]

Hi bmarkus,
can we expect the extension loading while booting will be the same as in x86* at some point?
And if so, is it at high or low priority?
In particular,  tce-bootload  currently isn't checking for  /usr/local/tce.installed/tcz-name
and files of extensions will be overwritten by those loaded later, which  tce-load  only does if the  -f  flag (force) is used.

[bmarkus]

In particular,  tce-bootload  currently isn't checking for  /usr/local/tce.installed/tcz-name
and files of extensions will be overwritten by those loaded later, which  tce-load  only does if the  -f  flag (force) is used.

Can you explain in details why current operation or tce-bootload is an issue and which case it causing a problem?

[Misalf]

With  tce-load  being is used for extension loading by  tce-setup , one can create big extensions out of smaller ones to reduce boot time and save RAM, because there are less loop mounts to be made (if the tce.installed scripts have been taken care of).
tce-bootload  loads extensions based only on the provided onboot.lst file, regardless of what is already loaded.

I might be wrong, but I think this also breaks or limits the functionality of built-in extensions (inside initrd).

[bmarkus]

With  tce-load  being is used for extension loading by  tce-setup , one can create big extensions out of smaller ones to reduce boot time and save RAM, because there are less loop mounts to be made (if the tce.installed scripts have been taken care of).
tce-bootload  loads extensions based only on the provided onboot.lst file, regardless of what is already loaded.

I might be wrong, but I think this also breaks or limits the functionality of built-in extensions (inside initrd).

Sorry, but still do not understand your problem.

[curaga]

He's mentioned before he embeds some extensions in the initrd to speed up boot. The tce.installed/ markers are included so that the extension is not loaded again, and it sounds like tce-bootload tries to load them again, defeating the speedup.

[Misalf]

curaga is correct, except that I did not embed extensions in the initrd but I have created an extension (100MB) containing many extensions I would usually load onboot. This saves about 15 seconds when using tce-load instead of tce-bootload in tce-setup.

Also the reported RAM usage right after boot goes from about 150MB down to 70MB.

It would be virtually the same result with extensions embedded in an initrd though.

For  tce-bootload  to behave more like  tce-load ...
1.) tce-bootload  should check for the existence of  /usr/local/tce.installed/extension-name  for each extension it loads. If respective tce.installed file exists, skip loading this extension.
2.) tce-bootload  should not overwrite files in tmpfs with files symlinked or copied from those contained in extensions.

[Paul_123]

If your not embedding an extension in the initrd.  How is there any thing located at /usr/local/tce.installed when tce-bootload runs?

[Misalf]

[...] one can create big extensions out of smaller ones to reduce boot time and save RAM, because there are less loop mounts to be made (if the tce.installed scripts have been taken care of).
[...]

I made sure that each extension contained inside the big one has a respective tce.installed file in order for that extension not being loaded again. Works on default Core.

[bmarkus]

Give me a link to download your big extension contains extensions for evaluation.

[Misalf]

I will prepare an  Xorg-big.tcz  for you and will upload it as soon as I have access to a faster internet connection.

[bmarkus]

I will prepare an  Xorg-big.tcz  for you and will upload it as soon as I have access to a faster internet connection.

Why do you made Xorg-bin.tcz, what is wront with the current Xorg in the repo?

[Misalf]

Sorry, bmarkus. You've misread my post. I said  Xorg-big  as in "not small", not  Xorg-bin  as in "binary".
With "-big" I wanted to imply that it's bigger than  Xorg.tcz , because it contains  Xorg.tcz  plus all its deps.

On top of that, I have the feeling that the language barrier gives us a hard time. English isn't my mother tong, so my wording might be confusing at times.