General TC > General TC Talk

TinyCore Editor (suite)

<< < (3/4) > >>

Roberto A. Foglietta:
Hi all,

The TinyCore Editor Suite version 0.4.0 has a fast lane to compile and include the last busybox into the distro.

Moreover, using busybox/busybox.sh update [suid|nosuid] it is possible to check quickly any modification to the busybox source code

https://github.com/robang74/tinycore-editor/archive/refs/tags/v0.4.0.tar.gz

Ciao,
-R

Roberto A. Foglietta:
Hi all,

TinyCore Editor version 0.4.4 runs in TinyCore.

https://github.com/robang74/tinycore-editor/archive/refs/tags/v0.4.4.tar.gz

So, you can compile busybox directly into TC, for example.

Choose "develop" in tinycore/tinycore.conf and follow the quick start in README.txt

Cheers,
-R

Roberto A. Foglietta:
Hi all,

 TinyCore Editor version 0.4.7 has been tested compatible with TinyCore (again).

 https://github.com/robang74/tinycore-editor/archive/refs/tags/v0.4.7.tar.gz

 It includes all the changes since v0.4.4 and still compatible.

 Cheers,
-R

Roberto A. Foglietta:
Hi all,

TinyCore Editor v0.4.8 it is able to recompile itself into the virtual guest 

https://github.com/robang74/tinycore-editor/archive/refs/tags/v0.4.8.tar.gz

Compatibility:
- TinyCore 12: tested ok (busybox recompiling is fine, native)
- Ubuntu 18.04: tested ok (busybox recompiling is acceptable)
- Ubuntu 20.04: tested ok (busybox recompiling inherits libcrypt-1.1.0)

The libcrypt-1.1.0 inheritance is not deeply tested yet but could be avoided:

- avoid to recompile busybox but only the ISO image
- use qemu and the ISO image to produce a native custom rootfs.gz
- transfer the native custom rootfs.gz via SSH and use it for any changes which are not involved with the busybox.

 After all, inheritance could be acceptable for testing busybox changes/developments but native compilation is the way to go.

Cheers, R-

Roberto A. Foglietta:
Hi,

 TinyCore Editor version 0.4.9 is able to build a 89 MB ISO/USB image that contains everything necessary to compile TinyCore Linux (compiletc.tz and more).

https://github.com/robang74/tinycore-editor/archive/refs/tags/v0.4.9.tar.gz

 Edit the meta packages in tinycore.conf including "develop" and "devtools". 

 Moreover - after having produced your first ISO you can do in tinycore folder sudo ./tczmetamerge.sh and all the packages will be aggregate in four meta-packages: sshonly, usbdisk, develop, devtools. This kind of configuration reduce drastically the boot time which arrives to be less than 9 seconds on a VirtualBox machine.

 For the 32bits architecture bridge-utils are still missing but they could be removed from develop.lst - they are useful to run qemu that in any case require X and it is not installed.

 I hope will enjoy it, R-

Navigation

[0] Message Index

[#] Next page

[*] Previous page