Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Final Releases => Topic started by: bmarkus on January 22, 2017, 02:43:00 AM
-
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
-
Wrong version string in
http://tinycorelinux.net/latest-armv6
http://tinycorelinux.net/latest-armv7
Warning:
You are running version 1.8.5
The latest release is 1.8.3
-
Wrong version string in
http://tinycorelinux.net/latest-armv6
http://tinycorelinux.net/latest-armv7
Warning:
You are running version 1.8.5
The latest release is 1.8.3
Thanks for reporting, fixed.
-
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.
-
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?
-
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).
-
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.
-
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.
-
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.
-
If your not embedding an extension in the initrd. How is there any thing located at /usr/local/tce.installed when tce-bootload runs?
-
[...] 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.
-
Give me a link to download your big extension contains extensions for evaluation.
-
I will prepare an Xorg-big.tcz for you and will upload it as soon as I have access to a faster internet connection.
-
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?
-
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.
-
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..
OK, I see. My fault, it was late ninght :)
-
Unfortunately, I haven't yet been able to upload my custom extension using a reliable internet connection.
Every time I try to upload it using my current internet connection the upload fails, which just eats my bandwidth data plan.
In the meantime, I hope the attached script will help you to create such an extension as I am using.
It extracts the extension (and its deps) specified by the -i option from /etc/sysconfig/tcedir/optional into the current working directory and creates an extension with a name specified by the -o option.
deps-merge.sh -i Xorg.tcz -o Xorg-all-deps.tcz
-
I found a bug or two while doing some more work on the script.
Shouldn't matter as my example to execute the script worked but just in case.
-
Great script Misalf!
I used it yesterday on a TinyCore (x86) to merge everything on the onboot.lst.
Doing so makes the boot process faster as well as memory consumption seems to drop (likely due to only one loopback device instead of >100)
Thanks again!!
Let me know if you have any updates to the script.
Pengo
-
Any idea how to get the Pi Zero W wifi working? The latest does not activate the wifi on the Zero W.
-
ZeroW is not supported until 9.x (unless you feel like hacking the boot partition)
-
Is there a way to update a running system remotely within 8.x version range?
-
Is there a way to update a running system remotely within 8.x version range?
Just replace every files in /mnt/mmcblk0p1/ except {config.txt, cmdline.txt, cmdline3.txt} and reboot