General TC > Programming & Scripting - Unofficial
ezremaster: Wizard that walks you step by step to remaster ISO of tinycore
ixbrian:
--- Quote from: littlebat on October 19, 2011, 05:26:03 AM ---Good work.
I found a question:
If I select "Extract TCZ to in to initrd”, ezremaster will not update "/lib/modules/*/modules.dep", for example, alsa-modules-*.tcz
So I add "sudo depmod -a -b $temp_dir/extract `uname -r` >/dev/null 2>&1; sudo ldconfig -r $temp_dir/extract >/dev/null 2>&1" at the head of "package()" function in file "/usr/local/bin/remaster.sh" to update "modules.dep" and "ld.so.cache".
--- End quote ---
Thanks for the info. I'll look at adding this in the next version of ezremaster.
littlebat:
After I “Extract TCZ to in to initrd” and get a remastered iso file, I found if I "tce-load -wi apackage" when running this remastered iso, it will download and install some packages I have extracted them into initrd already. So, I found a way to prevent this reduntant packages to be downloaded and installed as below. I think this can be an enhancement and may be an option when remastering.
1, Adding all the package flag file into "$temp_dir/extract/usr/local/tce.installed", if a tcz package missing tce.installed script then "touch packagename"(e.g., touch leafpad) for it. It can also delete every things in this folder if all the tce.installed script in tcz packages has been handled before "touch packagename" for every tcz packages extracted into initrd. This can be prevent the package to be installed again when it has been extracted into initrd.
2, "touch packagename.tcz" in "$temp_dir/extract/tmp/tce/optional" for every package to be extracted into initrd to prevent this package to be downloaded again.
3, Copy every needed *.dep file for the package has been extracted into initrd to prevent download dep file again.
ixbrian:
--- Quote from: littlebat on December 03, 2011, 10:54:45 PM ---After I “Extract TCZ to in to initrd” and get a remastered iso file, I found if I "tce-load -wi apackage" when running this remastered iso, it will download and install some packages I have extracted them into initrd already. So, I found a way to prevent this reduntant packages to be downloaded and installed as below. I think this can be an enhancement and may be an option when remastering.
1, Adding all the package flag file into "$temp_dir/extract/usr/local/tce.installed", if a tcz package missing tce.installed script then "touch packagename"(e.g., touch leafpad) for it. It can also delete every things in this folder if all the tce.installed script in tcz packages has been handled before "touch packagename" for every tcz packages extracted into initrd. This can be prevent the package to be installed again when it has been extracted into initrd.
2, "touch packagename.tcz" in "$temp_dir/extract/tmp/tce/optional" for every package to be extracted into initrd to prevent this package to be downloaded again.
3, Copy every needed *.dep file for the package has been extracted into initrd to prevent download dep file again.
--- End quote ---
I think the "Add extension inside initrd" would be the best option for what you are trying to do rather than trying to use the "Extract TCZ to initrd".
In my mind extracting extensions to the initrd works really well for making a single purpose appliance that you won't be adding additional packages to. Another really good case to use it is if you want extensions to be part of the "base" of your remaster so that when you boot with the "base" boot code they are still available. For example, I always extract "kmaps.tcz" to the initrd so that it is available even when booting "base".
But for normal day to day use where you are going to add a bunch of extensions down the road I would recommend one of the other 2 options other than "extract to initrd". Extracting to initrd completely bypasses all of the Tiny Core package management features/benefits.
If your suggestion was implemented it would likely cause issues when trying to use tools like AppsAudit. It sounds like for what you are trying to do your best option would be to use "Add extensions inside initrd".
Thanks,
Brian
coreplayer2:
--- Quote ---In my mind extracting extensions to the initrd works really well for making a single purpose appliance that you won't be adding additional packages to. Another really good case to use it is if you want extensions to be part of the "base" of your remaster so that when you boot with the "base" boot code they are still available. For example, I always extract "kmaps.tcz" to the initrd so that it is available even when booting "base".
But for normal day to day use where you are going to add a bunch of extensions down the road I would recommend one of the other 2 options other than "extract to initrd". Extracting to initrd completely bypasses all of the Tiny Core package management features/benefits.
--- End quote ---
EXACTLY!! I had the same problem actually, then realizing the issue was I didn't RTM, was simply attempting to build a system/iso with updatability by using a method designed for a one off build. There are options, "extract to initrd" is not one of them is all.
Isn't this the reason there is an "cde" option?? to keep extensions outside of initrd..?
Great app btw, thanks ixbrian for your time and great effort to produce this great tool. We appreciate it
gavs:
This tool looks like just what I need to create a music appliance. I have just started to explore it.
I noticed that version 2.0.3 was posted Dec 6. I am using a CD (/mnt/sr0) for the ISO source with Tinycore 4.1 . Version 2.0.2 got the necessary ISO files fine but version 2.0.3 gives an error that /mnt/sr0/boot/core.gz is not found. The ISO contains the file /mnt/sr0/boot/tinycore.gz.
Has the naming convention for the core changed? Should I download a new ISO (I have not tried changing the name on the ISO CD, not sure I can change it)?
gavs
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version