| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dcore:handling_extensions [2016/09/28 02:19] – [Miscellaneous SCE-related Files] nitram | dcore:handling_extensions [2018/07/13 15:25] (current) – volkerp |
|---|
| |
| ===== dCore SCE Overview ===== | ===== dCore SCE Overview ===== |
| |
| An SCE (self-contained extension) 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 [[http://wiki.tinycorelinux.net/dcore:sce-import_command|dCore sce-import Command]] is used to download files and create SCEs. | An SCE (self-contained extension) 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 [[http://wiki.tinycorelinux.net/dcore:sce-import_command|dCore sce-import Command]] is used to download files and create SCEs. |
| |
| |
| ===== dCore TCE (/tce/) Directory ===== | ===== dCore TCE (/tce/) Directory ===== |
| |
| The /tce/ (Tiny Core extension) directory is utilized to create and store SCE extensions. This is why the ''tce-setdrive'' command is used during installation to set up a persistent system. This allows extensions and related data to be stored for re-use, rather than having to re-install them with every fresh boot (ie. typical 'live' boot). The /etc/sysconfig/tcedir/ (/tce/) directory is actually a [[https://en.wikipedia.org/wiki/Symbolic_link|symbolic link]]. Exploring dCore's directory structure after installation will reveal that /etc/sysconfig/tcedir/ may be the same as /mnt/sda1/tce/ or whatever partition is used for the installation. | The /tce/ (Tiny Core extension) directory is utilized to create and store SCE extensions. This is why the ''tce-setdrive'' command is used during installation to set up a persistent system. This allows extensions and related data to be stored for re-use, rather than having to re-install them with every fresh boot (ie. typical 'live' boot). The /etc/sysconfig/tcedir/ (/tce/) directory is actually a [[https://en.wikipedia.org/wiki/Symbolic_link|symbolic link]]. Exploring dCore's directory structure after installation will reveal that /etc/sysconfig/tcedir/ may be the same as /mnt/sda1/tce/ or whatever partition is used for the installation. |
| |
| |
| ==== dCore Import (/tce/import/) Sub-Directory ==== | ==== dCore Import (/tce/import/) Sub-Directory ==== |
| |
| The /tce/import/ directory contains the sub-directories /debinx/ and /debs/. | The /tce/import/ directory contains the sub-directories /debinx/ and /debs/. |
| |
| The /tce/debinx/ directory contains numerous plain text database files used by dCore to import and update SCEs: | The /tce/import/debinx/ sub-directory contains numerous plain text database files used by dCore to import and update SCEs: |
| *KEEPDOC: Lists packages that should always keep documentation files when imported. | *KEEPDOC: Lists packages that should always keep documentation files when imported. |
| |
| *NEWDEBINX and OLDDEBINX: Both large files will be present if ''sce-update -a'' was previously run, which moves NEWDEBINX to OLDDEBINX and creates a fresh NEWDEBINX. They contain information on all packages in the dCore and Debian or Ubuntu repositories. Used and compared to determine whether updates are available. | *NEWDEBINX and OLDDEBINX: Both large files will be present if ''sce-update -a'' was previously run, which moves NEWDEBINX to OLDDEBINX and creates a fresh NEWDEBINX. They contain information on all packages in the dCore and Debian or Ubuntu repositories. Used and compared to determine whether updates are available. |
| |
| *PKDADDDEP: Lists extra dependencies for specific packages to help them run in dCore, from http://tinycorelinux.net/dCore/import/PKGADDDEP. | *PKGADDDEP: Lists extra dependencies for specific packages to help them run in dCore, from http://tinycorelinux.net/dCore/import/PKGADDDEP. |
| |
| *PKGDATAFILEMD5SUMLIST: An md5sum database of data and deb2sce files used during import, from http://tinycorelinux.net/dCore/import/PKGDATAFILEMD5SUMLIST. | *PKGDATAFILEMD5SUMLIST: An md5sum database of data and deb2sce files used during import, from http://tinycorelinux.net/dCore/import/PKGDATAFILEMD5SUMLIST. |
| **_main_i386_Packages and *_security_i386_Packages: See [[http://wiki.tinycorelinux.net/dcore:handling_extensions?&#dcore_repositories|dCore Repositories]] below. | **_main_i386_Packages and *_security_i386_Packages: See [[http://wiki.tinycorelinux.net/dcore:handling_extensions?&#dcore_repositories|dCore Repositories]] below. |
| |
| The /tce/debs/ sub-directory contains all *.deb and *.tar.gz files downloaded and utilized to import and update SCEs. As SCEs are updated or removed, over time the directory may contain deprecated files or those no longer needed by any existing SCE. These files can be purged to reclaim drive space using the [[http://wiki.tinycorelinux.net/dcore:sce-debpurge_command|dCore sce-debpurge Command]]. | The /tce/import/debs/ sub-directory contains all *.deb and *.tar.gz files downloaded and utilized to import and update SCEs. As SCEs are updated or removed, over time the directory may contain deprecated files or those no longer needed by any existing SCE. These files can be purged to reclaim drive space using the [[http://wiki.tinycorelinux.net/dcore:sce-debpurge_command|dCore sce-debpurge Command]]. |
| |
| ==== dCore OnDemand (/tce/ondemand/) Sub-Directory ==== | ==== dCore OnDemand (/tce/ondemand/) Sub-Directory ==== |
| |
| SCEs available OnDemand have startup scripts in /etc/sysconfig/tcedir/ondemand/. The script is automatically generated when the [[dCore:sce-import_command|dCore sce-import Command]] or [[dCore:sce-ondemand_command|dCore sce-ondemand Command]] is used to add a new or existing SCE to Ondemand (eg. ''sce-import -o firefox'', ''sce-ondemand firefox''). Example of a typical autogenerated OnDemand script: | SCEs available OnDemand have startup scripts in /etc/sysconfig/tcedir/ondemand/. The script is automatically generated when the [[dCore:sce-import_command|dCore sce-import Command]] or [[dCore:sce-ondemand_command|dCore sce-ondemand Command]] is used to add a new or existing SCE to Ondemand (eg. ''sce-import -o firefox'', ''sce-ondemand firefox''). Example of a typical autogenerated OnDemand script: |
| #!/bin/sh | #!/bin/sh |
| |
| ==== dCore SCE (/tce/sce/) Sub-Directory ==== | ==== dCore SCE (/tce/sce/) Sub-Directory ==== |
| |
| Imported SCEs are stored in /etc/sysconfig/tcedir/sce/ and only become usable when loaded. Each SCE extension will also have it's own *.sce.debinx and *.sce.md5.txt files. The *.sce.debinx file contains the md5sum of the /etc/sysconfig/tcedir/import/debinx/NEWDEBINX (Debian Index) database file used to create the SCE when first imported or re-imported during an update. This provides a quick update check mechanism. If the md5sum of a refreshed NEWDEBINX database file (refreshes when running ''sce-update'') still matches the md5sum listed in the SCE's *.sce.debinx file then the NEWDEBINX package database has not changed since the SCE was imported and a formal update check is not required. This is why an SCE update check sometimes completes almost instantaneously! | Imported SCEs are stored in /etc/sysconfig/tcedir/sce/ and only become usable when loaded. Each SCE extension will also have it's own *.sce.debinx and *.sce.md5.txt files. The *.sce.debinx file contains the md5sum of the /etc/sysconfig/tcedir/import/debinx/NEWDEBINX (Debian Index) database file used to create the SCE when first imported or re-imported during an update. This provides a quick update check mechanism. If the md5sum of a refreshed NEWDEBINX database file (refreshes when running ''sce-update'') still matches the md5sum listed in the SCE's *.sce.debinx file then the NEWDEBINX package database has not changed since the SCE was imported and a formal update check is not required. This is why an SCE update check sometimes completes almost instantaneously! |
| |
| The /sce/ directory also contains an /sce/update/ sub-directory, which is used to temporarily store updated SCEs until system reboot (see [[http://wiki.tinycorelinux.net/dcore:sce-update_command|dCore sce-update Command]]). To clarify, the /update/ sub-directory only contains updated SCEs when the outdated version was already loaded into RAM. If the SCE has not been loaded since boot, upon updating it will directly replace the old version in the /sce/ directory, rather than place it in the /update directory. So if an already loaded SCE is updated a reboot is necessary to use the updated version. However, if the SCE has not yet been loaded, then gets updated, loading the SCE after the update will load the updated version without the need to reboot. In reality it is more complex, as SCEs often contain the same dependencies as other SCEs, a non-updated and loaded extension may already have the outdated dependency loaded. For a security conscious user, the only true way to ensure all loaded libraries are fully up to date is to run [[http://wiki.tinycorelinux.net/dcore:sce-update_command|''sce-update -a'']] (update all SCEs) then reboot. | The /sce/ directory also contains an /sce/update/ sub-directory, which is used to temporarily store updated SCEs until system reboot (see [[http://wiki.tinycorelinux.net/dcore:sce-update_command|dCore sce-update Command]]). To clarify, the /update/ sub-directory only contains updated SCEs when the outdated version was already loaded into RAM. If the SCE has not been loaded since boot, upon updating it will directly replace the old version in the /sce/ directory, rather than place it in the /update directory. So if an already loaded SCE is updated a reboot is necessary to use the updated version. However, if the SCE has not yet been loaded, then gets updated, loading the SCE after the update will load the updated version without the need to reboot. In reality it is more complex, as SCEs often contain the same dependencies as other SCEs, a non-updated and loaded extension may already have the outdated dependency loaded. For a security conscious user, the only true way to ensure all loaded libraries are fully up to date is to run [[http://wiki.tinycorelinux.net/dcore:sce-update_command|''sce-update -a'']] (update all SCEs) then reboot. |
| |
| ===== dCore sceboot.lst ===== | **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** |
| |
| | ===== dCore sceboot.lst ===== |
| SCEs loaded at boot time are listed in /etc/sysconfig/tcedir/sceboot.lst. This replaces the "onboot" concept of Tiny Core. It should include any kernel modules and drivers required to run hardware and any extensions typically utilized at every boot. For most users this will include the X Window system (Xvesa or X.org), Xprogs (required for graphics), Alsa/sound, preferred Window Manager, web browser and file manager plus any firewall, networking and system monitoring extensions. | SCEs loaded at boot time are listed in /etc/sysconfig/tcedir/sceboot.lst. This replaces the "onboot" concept of Tiny Core. It should include any kernel modules and drivers required to run hardware and any extensions typically utilized at every boot. For most users this will include the X Window system (Xvesa or X.org), Xprogs (required for graphics), Alsa/sound, preferred Window Manager, web browser and file manager plus any firewall, networking and system monitoring extensions. |
| |
| # put other system startup commands here | # put other system startup commands here |
| /sbin/iptables-restore < /home/tc/iptables-config | /sbin/iptables-restore < /home/tc/iptables-config |
| | |
| | **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** |
| |
| ===== dCore Repositories ===== | ===== dCore Repositories ===== |
| </code> | </code> |
| |
| Each of these repositories will become accessible via the [[dCore:sce-import_command|dCore sce-import Command]] to search and install the desired software. Visit the [[http://forum.tinycorelinux.net/index.php/board,75.0.html|dCore Extra Repositories]] sub-forum for more information. | Each of these repositories will become accessible via the [[dCore:sce-import_command|dCore sce-import Command]] to search and install the desired software. Note a /opt/debextra/ entry can be disabled by commenting out (use #) the desired entry, allowing selective use of extra repositories, example: |
| | #http://ppa.launchpad.net/niko2040/e19/ubuntu wily main |
| | |
| | Visit the [[http://forum.tinycorelinux.net/index.php/board,75.0.html|dCore Extra Repositories]] sub-forum for more information. |
| |
| ==== Repository Processing Order ==== | ==== Repository Processing Order ==== |
| Extra repositories in /opt/debextra/ take precedence over the standard Debian and Ubuntu repositories when importing software. As there is currently no automated mechanism to compare available software versions between repositories, these /opt/debextra/ debinx files are processed in ASCII sorting order for preferential processing. They can be named numerically, as the above example, or however the user wishes. The first correct package name hit when sequentially processing the repositories will be imported. | Extra repositories in /opt/debextra/ take precedence over the standard Debian and Ubuntu repositories when importing software. As there is currently no automated mechanism to compare available software versions between repositories, these /opt/debextra/ debinx files are processed in ASCII sorting order for preferential processing. They can be named numerically, as the above example, or however the user wishes. The first correct package name hit when sequentially processing the repositories will be imported. |
| | |
| | **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** |
| |
| ===== Miscellaneous SCE-related Files ===== | ===== Miscellaneous SCE-related Files ===== |
