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
wiki:remastering_kmap_iso [2013/01/17 10:47] – added remark about using the remaster.sh skript bernhardwiki:remastering_kmap_iso [2018/09/07 11:13] (current) – FAQ link moved from ibiblio.org to tinycorelinux.net, Syslinux link wrapped bernhard
Line 3: Line 3:
 CorePlus supports international keyboard layout with the boot option kmap=qwertz/de-latin1 (german keyboard layout is given here as an example).  CorePlus supports international keyboard layout with the boot option kmap=qwertz/de-latin1 (german keyboard layout is given here as an example). 
  
-Starting with Core v4.4 (or more exactly, with release candidate 3 of V4.4) it is possible to put CorePlus.iso on an USB stick and boot that image via memdisk. Memdisk is part of the syslinux project (see [[http://www.syslinux.org/wiki/index.php/MEMDISK#ISO_images]]); it emulates a bios hard disk, which accesses the ISO image. When the native hard disk drivers take over, the operating system has to support the access of the ISO image. For that purpose a boot option iso=<device> (e.g. iso=sdb1, see corresponding [[http://distro.ibiblio.org/tinycorelinux/faq.html#iso|FAQ]]) was added to TinyCore. In example iso=sdb1 TinyCore searches sdb1 for files with extension iso and uses the first image found, mounts that image (in the hope that it is the Core image). If there are several files with extension iso, the full path must be specified, i.e. iso=sdb1/TinyCore/CorePlus.iso as a example, which I tested). +Starting with Core v4.4 (or more exactly, with release candidate 3 of V4.4) it is possible to put CorePlus.iso on an USB stick and boot that image via memdisk. Memdisk is part of the syslinux project (see [[http://www.syslinux.org/wiki/index.php/MEMDISK#ISO_images|Syslinux docu]]); it emulates a bios hard disk, which accesses the ISO image. When the native hard disk drivers take over, the operating system has to support the access of the ISO image. For that purpose a boot option iso=<device> (e.g. iso=sdb1, see corresponding [[http://tinycorelinux.net/faq.html#iso|FAQ]]) was added to TinyCore. In example iso=sdb1 TinyCore searches sdb1 for files with extension iso and uses the first image found, mounts that image (in the hope that it is the Core image). If there are several files with extension iso, the full path must be specified, i.e. iso=sdb1/TinyCore/CorePlus.iso as a example, which I tested). 
  
 Since it is tedious to type in these boot parameters every time, I remastered successfully the image and would like to share my experience here. Since it is tedious to type in these boot parameters every time, I remastered successfully the image and would like to share my experience here.
Line 22: Line 22:
  
 {{:wiki:extension.png|add extensions}} {{:wiki:extension.png|add extensions}}
- 
-Click next (or add some scm extensions and click next). 
- 
-{{:wiki:scmextensioncropped.png|add extensions}} 
  
 Click next. Click next.
Line 43: Line 39:
  ''remaster.sh /mnt/sda2/TC/ezremaster.cfg rebuild''  ''remaster.sh /mnt/sda2/TC/ezremaster.cfg rebuild''
  
-in a terminal window.+in a terminal window. If you are updating only to a newer version, you might edit the ''ezremaster.cfg'' and replace ''CorePlus-4.7.7.iso'' by ''CorePlus-5.0.iso'' (as an example).
  
 done. done.
Print/export
QR Code
QR Code wiki:remastering_kmap_iso (generated for current page)