| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dcore:extension_strategies [2016/12/26 06:24] – [Locales and Languages] nitram | dcore:extension_strategies [2018/12/11 08:14] (current) – [Locales and Languages] link inserted sm8ps |
|---|
| |
| ===== Boot Code nomd5 ===== | ===== Boot Code nomd5 ===== |
| The nomd5 boot code skips md5sum cheking 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 the 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. | 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 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. | 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]]** |
