| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dcore:comparison_to_tinycore [2016/05/09 03:54] – [dCore] nitram | dcore:comparison_to_tinycore [2016/05/09 03:59] (current) – [Tiny Core] nitram |
|---|
| |
| ==== Tiny Core ==== | ==== Tiny Core ==== |
| Tiny Core utilizes '.tcz' extensions [[http://forum.tinycorelinux.net/index.php/topic,15612.msg91178.html#msg91178|(not supported by dCore)]]. In the [[http://tinycorelinux.net/book.html|Into the Core book]], '.tcz' extensions are described as loop-mounted squashfs archives, with specified parameters, | Tiny Core utilizes TCZ extensions [[http://forum.tinycorelinux.net/index.php/topic,15612.msg91178.html#msg91178|(not supported by dCore)]]. In the [[http://tinycorelinux.net/book.html|Into the Core book]], TCZ extensions (type .tcz) are described as loop-mounted squashfs archives, with specified parameters, |
| usually symlinked into the main file system. The archive can be either mounted and symlinked or copied to the file system (usually RAM) for faster execution. It consists of the direct file system tree that can be found when installing an application or library. It usually consists of the binary, desktop file, program icon and any required data files. These '.tcz' extensions are compiled by either a Tiny Core Linux developer or a user-contributor and are usually retrieved from Tiny Core's repositories using the Apps utility. Each '.tcz' is a single application or library that usually requires other '.tcz' extensions for functionality (ie. dependencies). Applying software updates requires re-compiling the relevant extension(s) and upgrading through Apps. | usually symlinked into the main file system. The archive can be either mounted and symlinked or copied to the file system (usually RAM) for faster execution. It consists of the direct file system tree that can be found when installing an application or library. It usually consists of the binary, desktop file, program icon and any required data files. These extensions are compiled by either a Tiny Core Linux developer or a user-contributor and are usually retrieved from Tiny Core's repositories using the Apps utility. Each TCZ is a single application or library that usually requires other TCZ extensions for functionality (ie. dependencies). Applying software updates requires re-compiling the relevant extension(s) and/or upgrading through Apps. |
| |
| A Tiny Core Linux extension description from ragingpenguin.com is quoted below (link not available). Tiny Core Linux continues to utilize the '.tcz' extension format, although the '.scm' extension format no longer appears to be utilized. | A Tiny Core extension description from ragingpenguin.com is quoted below (link not available). Tiny Core continues to utilize the TCZ extension format, although SCM extensions no longer appear to be utilized. |
| |
| >"The TCZ extension system appears to be based on the original MyDSL system made by Robert [Shingledecker, editor's note], and it works in much the same way. That means packages are attached to a temporary layered filesystem during boot, instead of being extracted directly into a permanent root directory. The packages themselves are read-only Squashfs archives, and can either be loaded into RAM for a performance boost, or just mounted. TCZ extensions can be considered "normal" packages. That is, they have dependencies, config files, and in some cases, they may even have setup scripts. | >"The TCZ extension system appears to be based on the original MyDSL system made by Robert [Shingledecker, editor's note], and it works in much the same way. That means packages are attached to a temporary layered filesystem during boot, instead of being extracted directly into a permanent root directory. The packages themselves are read-only Squashfs archives, and can either be loaded into RAM for a performance boost, or just mounted. TCZ extensions can be considered "normal" packages. That is, they have dependencies, config files, and in some cases, they may even have setup scripts. |
