Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
dcore:comparison_to_tinycore [2016/05/09 03:57] – [Tiny Core] nitram | dcore:comparison_to_tinycore [2016/05/09 03:59] (current) – [Tiny Core] nitram | ||
---|---|---|---|
Line 5: | Line 5: | ||
==== Tiny Core ==== | ==== Tiny Core ==== | ||
- | Tiny Core utilizes TCZ extensions [[http:// | + | Tiny Core utilizes TCZ extensions [[http:// |
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. | 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. | ||