Welcome to the Tiny Core Linux Wiki at tinycorelinux.net!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dcore:comparison_to_tinycore [2016/05/08 16:20]
nitram [dCore vs Tiny Core Extensions]
dcore:comparison_to_tinycore [2016/05/09 00:59] (current)
nitram [Tiny Core]
Line 2: Line 2:
 Based on Micro Core, dCore shares the same [[dcore:concepts|basic concepts]] and a similar minimal base. Just as Tiny Core is essentially Micro Core with additional extensions and a graphic environment, dCore also has a minimal base that is capable of importing extensions and booting into a graphic environment. Based on Micro Core, dCore shares the same [[dcore:concepts|basic concepts]] and a similar minimal base. Just as Tiny Core is essentially Micro Core with additional extensions and a graphic environment, dCore also has a minimal base that is capable of importing extensions and booting into a graphic environment.
  
-There are, however, several differences. The most obvious is how dCore handles packages and creates extensions. Unlike Tiny Core, dCore is capable of importing packages directly from Debian or Ubuntu repositories, no need to compile software. Thus dCore can be thought of as *Core with access to the enormous realm of Debian or Ubuntu repositories.+There are, however, several differences. The most obvious is how dCore handles packages and creates extensions. Unlike Tiny Core, dCore is capable of importing packages directly from Debian or Ubuntu repositories. Thus dCore can be thought of as *Core with access to the enormous realm of Debian or Ubuntu repositories.
  
-dCore uses the [[http://wiki.tinycorelinux.net/dcore:sce-import#deb2sce|deb2sce script]] to transform Debian or Ubuntu packages into SCE extensions (self-contained extensions, type '.sce'). This differs from Tiny Core, which utilizes '.tcz' extensions [[http://forum.tinycorelinux.net/index.php/topic,15612.msg91178.html#msg91178|(not supported by dCore)]]. +==== Tiny Core ==== 
-==== TinyCore ==== +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, 
-A dated description of Tiny Core Linux extension formats taken from ragingpenguin.com (link not longer unavailableis outlined belowTiny Core Linux continues to utilize the '.tcz' extension format, although the '.scm' extension format no longer appears to be utilized.+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 utilityEach 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.
  
-"The TCZ extension system appears to be based on the original MyDSL system made by Robert [Shingledeckereditor'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.+A Tiny Core extension description from ragingpenguin.com is quoted below (link not available). Tiny Core continues to utilize the TCZ extension formatalthough SCM extensions no longer appear to be utilized.
  
-SCM extensions function like mount-only TCZs. SCM stands for Self Contained Module. It is basically a resurrection of the old .uci compressed image system that Robert made for DSLexcept now the package files are SquashFS archivesBecause SCMs are self contained, the packager or developer is free to experiment with hazardous or unavailable librariesbinaries, and scripts without breaking other parts of the systemSome SCMs may contain multiple binaries or libraries that are meant to work together. For examplean SCM for a media player may contain a lot of codecs and most (if not all) of the dependencies required for it to runOther than thatSCMs can have dependencies, config files, and setup scripts just like TCZs."+>"The TCZ extension system appears to be based on the original MyDSL system made by Robert [Shingledeckereditor's note], and it works in much the same wayThat means packages are attached to a temporary layered filesystem during bootinstead of being extracted directly into a permanent root directoryThe packages themselves are read-only Squashfs archivesand can either be loaded into RAM for a performance boost, or just mountedTCZ extensions can be considered "normal" packages. That isthey have dependencies, config files, and in some cases, they may even have setup scripts.
  
 +>SCM extensions function like mount-only TCZs. SCM stands for Self Contained Module. It is basically a resurrection of the old .uci compressed image system that Robert made for DSL, except now the package files are SquashFS archives. Because SCMs are self contained, the packager or developer is free to experiment with hazardous or unavailable libraries, binaries, and scripts without breaking other parts of the system. Some SCMs may contain multiple binaries or libraries that are meant to work together. For example, an SCM for a media player may contain a lot of codecs and most (if not all) of the dependencies required for it to run. Other than that, SCMs can have dependencies, config files, and setup scripts just like TCZs."
 ==== dCore ==== ==== dCore ====
-Unlike Tiny Core, dCore does not utilize single pre-bundled '.tcz' extensions from the *Core repositories. Instead it pulls in all necessary Debian or Ubuntu packages from their repositories and converts them into a single SCE (self-contained extension). An SCE, therefore, consists of a converted Debian package and all it's dependencies, packed into it's own file system and compressed into a single file (SquashFS). The contents of an SCE are transparent and once mounted can be inspected by exploring /tmp/tcloop/, otherwise copy the extension to a temporary directory and run unsquashfs SCE. 
  
-**[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore wiki welcome page]]**+dCore uses the [[http://wiki.tinycorelinux.net/dcore:sce-import#deb2sce|deb2sce script]] to transform Debian or Ubuntu packages into SCE extensions (self-contained extensions, type '.sce'). An SCE, therefore, consists of a converted Debian package and all it's dependencies, packed into it's own file system and compressed into a single file (SquashFS). This is similar to the SCM extension format quoted above. The contents of an SCE are transparent and once mounted can be inspected by exploring /tmp/tcloop/, otherwise copy the extension to a temporary directory and run unsquashfs SCE. The ''sce-update'' command is used to check SCE(s) for updates, which calls ''sce-import'' to re-import the updated extension. Like Tiny Core, a reboot is necessary to apply updates if the old version extension has already been loaded into RAM for usage. 
 + 
 + 
 +**[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
Print/export