You are here: welcome » dcore » extension_strategies

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
dcore:extension_strategies [2016/11/07 23:52] – [Creating Personal Extensions] nitramdcore:extension_strategies [2018/12/11 08:14] (current) – [Locales and Languages] link inserted sm8ps
Line 1: Line 1:
 ====== Advanced dCore SCE Strategies ====== ====== Advanced dCore SCE Strategies ======
- 
-**>> UNDER RENOVATION <<** 
  
 ===== Overview ===== ===== Overview =====
Line 237: Line 235:
  
 http://forum.tinycorelinux.net/index.php/topic,20413.msg127208.html#msg127208 http://forum.tinycorelinux.net/index.php/topic,20413.msg127208.html#msg127208
 +
 +**[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
 +
 +===== Boot Code nomd5 =====
 +The nomd5 boot code skips md5sum checking of boot time SCEs, slightly improving boot speed. Loading SCEs during runtime, using ''sce-load'' and OnDemand, will also be slightly faster. In a test system, using the nomd5 boot code resulted in a 6% faster boot time (measured from boot loader to boot screen). To determine approximate boot time improvement, run ''time /bb/md5sum SCE.sce'' against all sceboot.lst SCEs. The combined total of these timed md5sum tests will give the approximate boot time improvement.
 +
 +By default SCE md5sum checks are performed during loading to ensure SCE integrity. As such, the nomd5 boot code should not be used if there are system security concerns, such as potential tampering within the SCE directory. For systems with high security priority, the SCE *.md5.txt files could be saved securely and periodically checked against the actual extension. The process could be automated using a relatively simple script. This backup and check process would need to be repeated whenever SCEs are updated.
  
 **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
  
 ===== Locales and Languages ===== ===== Locales and Languages =====
-*insert locale wiki page link here+* cf. relevant [[http://wiki.tinycorelinux.net/dcore:installations#dcore_localisation|wiki pages]]
  
 **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
Line 304: Line 309:
  
 # UPDATEDEBINXMODE is default and not needed to be specified here. # UPDATEDEBINXMODE is default and not needed to be specified here.
 +
 +# Use SAFEBACKUP=TRUE to backup SCE(s) in /etc/sysconfig/tcedir/sce/backup/
 +# during re-import. Ensure adequate freespace, manually purge backups.
 +SAFEBACKUP=FALSE
  
 # Use NICE=19 for the most cpu friendly use of sce-import and sce-update.   # Use NICE=19 for the most cpu friendly use of sce-import and sce-update.  
Line 317: Line 326:
  
 ===== Version Conflicts ===== ===== Version Conflicts =====
-Contrary to the above-said, there does exist some potential for conflicts between different versions of one and the same package in different extensions. Thus it is important to keep the extensions up to date by [[dcore:handling_extensions#sce-update]].+As SCEs are self-contained the potential for dependency version conflicts between loaded SCEs exist. If different SCEs have a common dependency, a frequent occurrence, but were not imported or updated at the same time, one SCE may still be using an older dependency version while another has the updated version. 
 + 
 +Although rare, this may cause extension breakage if two or more SCEs with out of sync dependency versions are loaded at the same time. More concerning is a potential security issue, as there is no guarantee loaded SCEs that use common dependencies are all using the most up to date security releases. 
 + 
 +Strategies to avoid dependency version conflicts: 
 +  * Import all SCEs using list file(s) and/or dependency chains to minimize dependency duplication (discussed above). 
 +  * Periodically run ''sce-update -a'' (see [[http://wiki.tinycorelinux.net/dcore:sce-update_command|dCore sce-update Command]]) to ensure all SCEs are updated at the same time. 
 +  * Periodically manually re-import all SCEs. The ''sce-update'' check process is CPU intensive and most SCEs will receive security updates during a longer time frame. If the SCEs were not update checked for some time, it may be quickest to periodically re-import all system SCEs manually, for example monthly. The re-import will ensure updated dependencies are utilized.
  
 ===== Broken SCEs ===== ===== Broken SCEs =====
Print/export
QR Code
QR Code dcore:extension_strategies (generated for current page)