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

wiki:remastering [2011/05/05 14:37]
127.0.0.1 external edit
wiki:remastering [2015/09/17 17:42] (current)
mzs.112000 Updated file names because the new releases are different
Line 13: Line 13:
 ===== Unpacking ===== ===== Unpacking =====
  
-First, get the kernel and ''tinycore.gz'' from the iso:+First, get the kernel and ''core.gz'' from the iso:
  
 <code>sudo mkdir /mnt/tmp <code>sudo mkdir /mnt/tmp
 sudo mount tinycore.iso /mnt/tmp -o loop,ro sudo mount tinycore.iso /mnt/tmp -o loop,ro
-cp /mnt/tmp/boot/bzImage /mnt/tmp/boot/tinycore.gz /tmp+cp /mnt/tmp/boot/vmlinuz /mnt/tmp/boot/core.gz /tmp
 sudo umount /mnt/tmp</code> sudo umount /mnt/tmp</code>
  
Line 28: Line 28:
 sudo umount /mnt/tmp</code> sudo umount /mnt/tmp</code>
  
-Then, extract ''tinycore.gz'' for adding/removing something:+Then, extract ''core.gz'' for adding/removing something:
  
 <code>mkdir /tmp/extract <code>mkdir /tmp/extract
 cd /tmp/extract cd /tmp/extract
-zcat /tmp/tinycore.gz | sudo cpio -i -H newc -d</code>+zcat /tmp/core.gz | sudo cpio -i -H newc -d</code>
  
 Now, the full filesystem is in ''/tmp/extract''. Feel free to add, remove, or edit anything you like. Now, the full filesystem is in ''/tmp/extract''. Feel free to add, remove, or edit anything you like.
Line 39: Line 39:
  
 As per [[http://forum.tinycorelinux.net/index.php?topic=8437.0 | Forum topic - Overlay using cat ]] an interesting alternative to unpacking, editing and repacking files is simply to, using the cat command, concatenate multiple gzipped cpio archives together.   As per [[http://forum.tinycorelinux.net/index.php?topic=8437.0 | Forum topic - Overlay using cat ]] an interesting alternative to unpacking, editing and repacking files is simply to, using the cat command, concatenate multiple gzipped cpio archives together.  
 +
 +You should be aware that this way results in a slightly slower boot, and likely bigger initramfs size.
  
 For example:  For example: 
Line 53: Line 55:
 You must use chroot because "depmod -b /tmp/extract" will not follow the kernel.tclocal symbolic link to find modules under /usr/local. You must use chroot because "depmod -b /tmp/extract" will not follow the kernel.tclocal symbolic link to find modules under /usr/local.
  
-For versions 2.x where x >= 2 and later: +For versions 2.x where x >= 2 and later (replace the kernel uname with the right one)
-<code>sudo depmod -b /tmp/extract 2.6.29.1-tinycore</code>+<code>sudo depmod -a -b /tmp/extract 2.6.29.1-tinycore</code>
  
 If you added shared libraries then execute If you added shared libraries then execute
Line 65: Line 67:
 cd /tmp cd /tmp
 advdef -z4 tinycore.gz</code> advdef -z4 tinycore.gz</code>
 +    
 It is packed at level 2 to save time. advdef -z4 is equivalent to about -11 on gzip. It is packed at level 2 to save time. advdef -z4 is equivalent to about -11 on gzip.
  
Line 91: Line 93:
  
 You may find [[http://www.littlesvr.ca/isomaster/|ISO Master]] useful. Its a GUI disk image editing tool, available in the repository as a .tcz extension. You may find [[http://www.littlesvr.ca/isomaster/|ISO Master]] useful. Its a GUI disk image editing tool, available in the repository as a .tcz extension.
 +
 +
 +===== Possible Errors When Booting =====
 +
 +  * //Loading /boot/vmlinuz....
 +     Could not find ramdisk image: /boot/<myrdimg>.gz//  
 +    - There seems to be a limit on the number of characters in the name of the ramdisk image file (if it's >= 10 chars it failed for all my tries, but 7 chars worked).
  
 [[wiki:dynamic_root_filesystem_remastering|Follow dynamic root fs remastering here]] [[wiki:dynamic_root_filesystem_remastering|Follow dynamic root fs remastering here]]
Print/export