Both sides previous revisionPrevious revision | |
wiki:remastering_with_ezremaster [2011/11/16 23:13] – ixbrian | wiki:remastering_with_ezremaster [2024/07/06 16:35] (current) – external edit 127.0.0.1 |
---|
| |
| |
====== Overview ====== | ====== Overview ====== |
| |
ezremaster is an GUI application that simplifies remastering Tiny Core or Micro Core Linux. It is free software released under the GPLv2 license. | ezremaster is a GUI application that simplifies remastering Tiny Core or Micro Core Linux. It is free software released under the GPLv2 license. |
| |
It supports the following features | It supports the following features: |
| |
* Setting all of the bootcodes | * Setting all of the bootcodes |
* Adding a mydata.tgz to the remaster | * Adding a mydata.tgz to the remaster |
* Easily recreating your custom ISO image when new versions of Tiny Core are released | * Easily recreating your custom ISO image when new versions of Tiny Core are released |
%%% | |
%%% | |
| |
====== Installation ====== | ====== Installation ====== |
| Boot up Tiny Core Linux, start up the Application Browser, and search and install "ezremaster". Once installed, you can open a terminal window and type "ezremaster" which will start the GUI. |
Boot up Tiny Core Linux, start up the Application Browser, and search and install "ezremaster". Once installed, you can open a terminal window and type "ezremaster" which will start the GUI. | |
%%% | |
%%% | |
| |
====== Options for adding extensions to your remaster ====== | ====== Options for adding extensions to your remaster ====== |
| ezremaster supports several methods of adding extensions to your remaster, each with their benefits and drawbacks. The 3 methods can be mixed. |
| |
ezremaster supports several methods of adding extensions to your remaster, each with their benefits and drawbacks. The 3 methods can be mixed. | **"Outside initrd apps on boot" / "Outside initrd apps"**: These options will put the extensions in the ISO image under /tce/optional. |
| If you use "Outside initrd apps on boot" the extension will also be listed in /tce/optional/onboot.lst so that the extension is automatically loaded at boot. |
| The "Outside initrd" options are best for systems that have limited memory but you must leave the remaster CD in the drive after booting. |
| There is also an option "Check to optionally set copy2fs.flg if using outside initrd apps". |
| This option creates the copy2fs.flg which will cause the extensions to be copied to memory at bootup which will require more memory but will allow you to remove the CD after booting. |
| |
**"Outside initrd apps on boot" / "Outside initrd apps"**: These options will put the extensions in the ISO image under /tce/optional. If you use "Outside initrd apps on boot" the extension will also be listed in /tce/optional/onboot.lst so that the extension is automatically loaded at boot. The "Outside initrd" options are best for systems that have limited memory but you must leave the remaster CD in the drive after booting. There is also an option "Check to optionally set copy2fs.flg if using outside initrd apps". This option creates the copy2fs.flg which will cause the extensions to be copied to memory at bootup which will require more memory but will allow you to remove the CD after booting. | **"Inside initrd apps on boot" / "Inside initrd apps"**: These options will but the extensions in the initrd (tinycore.gz) under /opt/tce/optional. |
| If you use "Inside initrd apps on boot" the extension will also be listed in the /opt/tce/optional/onboot.lst so that the extension is automatically loaded at boot. |
| The result is a system that boots entirely from memory and the CD can be removed as soon as Tiny Core starts booting. This is a good method to use if you have enough memory on your system. |
| |
**"Inside initrd apps on boot" / "Inside initrd apps":** These options will but the extensions in the initrd (tinycore.gz) under /opt/tce/optional. If you use "Inside initrd apps on boot" the extension will also be listed in the /opt/tce/optional/onboot.lst so that the extension is automatically loaded at boot. The result is a system that boots entirely from memory and the CD can be removed as soon as Tiny Core starts booting. This is a good method to use if you have enough memory on your system. | **"Extract TCZ to in to initrd"**: With this method, during the remaster process each extension you selected will be mounted and then copied in to the extracted initrd. |
| The result is a system that loads everything to memory (CD can be removed after system starts booting) and which boots faster than the "inside initrd apps" method. |
**"Extract TCZ to in to initrd":** With this method, during the remaster process each extension you selected will be mounted and then copied in to the extracted initrd. The result is a system that loads everything to memory (CD can be removed after system starts booting) and which boots faster than the "inside initrd apps" method. Since the extensions are no longer mounted, compressed TCZ files (squashfs) as they are with the "Inside initrd apps" this method takes slightly more memory but should have better performance. | Since the extensions are no longer mounted, compressed TCZ files (squashfs) as they are with the "Inside initrd apps" this method takes slightly more memory but should have better performance. |
%%% | |
%%% | |
| |
====== Planned features for future releases ====== | ====== Planned features for future releases ====== |
| * Support "ondemand" extensions in remasters. |
* Support "ondemand" extensions in remasters. | |
%%% | |
%%% | |
| |
====== Troubleshooting ====== | ====== Troubleshooting ====== |
| * On the first page of the wizard, you set the "Path to temporary work directory" which defaults to "/tmp/ezremaster". |
* On the first page of the wizard, you set the "Path to temporary work directory" which defaults to "/tmp/ezremaster". If you are making a large remaster (adding lots of extensions) and have limited memory, you will want to change this from a RAM based location (like default /tmp) to a directory on a mounted hard drive. To do this, mount a hard drive (example mount /mnt/hda1), and create a directory and set permissions (sudo mkdir /mnt/hda1/ezremaster; sudo chown tc.staff /mnt/hda1/ezremaster) | If you are making a large remaster (adding lots of extensions) and have limited memory, you will want to change this from |
%%% | a RAM based location (like default /tmp) to a directory on a mounted hard drive. To do this, mount a hard drive |
%%% | (example mount /mnt/hda1), and create a directory and set permissions (sudo mkdir /mnt/hda1/ezremaster; sudo chown tc.staff /mnt/hda1/ezremaster) |
| |
====== Questions/Comments/Suggestions/Feature Requests ====== | ====== Questions/Comments/Suggestions/Feature Requests ====== |
| |
Use the existing forum thread at: http://forum.tinycorelinux.net/index.php?topic=6645.0 | Use the existing forum thread at: http://forum.tinycorelinux.net/index.php?topic=6645.0 |
%%% | |
%%% | |
| |
====== Screenshots ====== | ====== Screenshots ====== |
Intro Screen:%%% | |Intro Screen| |
{{wiki:twid_35_ezremaster_intro.jpg}} | |{{wiki:twid_35_ezremaster_intro.jpg}}| |
| |
| |Bootcode selection Screen| |
| |{{wiki:twid_34_ezremaster_bootcodes.jpg}}| |
| |
| |Extension selection Screen| |
| |{{wiki:twid_33_ezremaster_apps.jpg}}| |
| |
Bootcode selection Screen:%%% | |Remaster Step #1 Screen| |
{{wiki:twid_34_ezremaster_bootcodes.jpg}} | |{{wiki:twid_36_ezremaster_remaster.jpg}}| |
| |
Extension selection Screen:%%% | |
{{wiki:twid_33_ezremaster_apps.jpg}} | |
| |
Remaster Step #1 Screen:%%% | |
{{wiki:twid_36_ezremaster_remaster.jpg}} | |