extensions load from iso in VM but not once burned to CD

[Jason W]

I have already written a script that takes your existing tce directory and creates an opt_tce.gz out of the contents and creates an iso based on an already downloaded release iso.  In other words, be running TC, mount install your favorite apps through the appbrowser, download a release iso, then run the script and it spits out a premade iso with those extensions integrated in /opt/tce.  A warning message appears indicating the RAM the extensions will occupy not counting run time use.  

I used the method mentioned by danielbarnes that keeps the opt_tce initrd seperate so it is easy to just copy that file and the isolinux.cfg from one release to another.  I may consider putting a GUI to this, maybe Xdialog, but that is really not needed as there is only one step involved and that is choosing the base iso you want to start with.   After some more testing I may post in the programming and scripting section.

I may add an option to include your backup as well if /opt/tce supports it so the cd could be fairly personalized.  While providing a prebuilt desktop is not what TC is about, I know there are times when a preinstalled cd is desired.  I was using a Windows machine away from home for a while where I had no Linux access to the hard drive and the usb ports were no longer working.  I got tired of redownloading all the extensions I normally use as well as having no saved settings, so I made a cd a while back.  It made life easier, and I think a tool to make it easy to make a custom iso would be practical for those who want it.

[danielibarnes]

I think a tool to make it easy to make a custom iso would be practical for those who want it.

I think that sentence summarizes this and numerous other threads on the same topic. I would add that while a GUI front-end may not add any features, it makes the tool more accessible to those who fear the command line.

I have already written a script that takes your existing tce directory and creates an opt_tce.gz out of the contents and creates an iso based on an already downloaded release iso.

I used the method mentioned by danielbarnes that keeps the opt_tce initrd seperate so it is easy to just copy that file and the isolinux.cfg from one release to another.

It would be worthwhile then for the script to accept an existing opt_tce.gz (or automatically extract it from a previously customized iso) and migrate that to a new release.

[tclfan]

Jason, Danielibarnes,
This is greatly appreciated! Your work that is, to make this easier for TC users. Also your words confirm recognition that this is an important tool for TC...

[jur]

I would add that while a GUI front-end may not add any features, it makes the tool more accessible to those who fear the command line.

I have seen this sort of statement many times in many places... the implication is there is some sort of irrational idea of not wanting to use the command line. May be tongue in cheek, but a word in jest is oft based on some serious idea...

In any case as a newcomer to linux it isn't that I "fear the command line", no it is simply lack of knowledge of the thousands(?) of commands, each with their switches that take years to master. A GUI is simply for making things easier. Clicking a few buttons is a lot easier than trying to discover the right series of command plus their switches.

[Jason W]

I have most details in place, will test some things tonight.  I don't want to promote creating custom cd's as a normal means of running TC, but rather as a special purpose tool.  Say for instance creating a rescue cd with some basic tools installed.  Or a basic desktop of a small set of one's favorite apps to keep as a backup system.

I think users of all experience levels would in general be much better off having their backup and tce directory on persistent writable storage for general use.  But I will try to provide a simple way to remaster using /opt/tce if it can be done elegantly and in keeping with TC concepts and supported running modes.  

[danielibarnes]

In any case as a newcomer to linux it isn't that I "fear the command line", no it is simply lack of knowledge of the thousands(?) of commands, each with their switches that take years to master.

That is true also. Years is not an exaggeration. I find these links indispensable, among others:
Linux Command Directory
Bash man page

I don't want to promote creating custom cd's as a normal means of running TC, but rather as a special purpose tool.

If I had a nickel for every time I saw someone ask about remastering TC ... heh. Some didn't need to remaster, but only thought they did. If a tool is easy to use, then it is likely that some will try to use it without understanding it first. I think that with sufficient documentation regarding usage though, users will recognize it as special-purpose, like TC_Terminal_Server. It took me a while before I realized that "become a mothership" meant running a DHCP/TFTP server for PXE.

[Guy]

I have already written a script that takes your existing tce directory and creates an opt_tce.gz out of the contents and creates an iso based on an already downloaded release iso.

Jason

Compare the time it takes to boot with the same extensions integrated using this method.
http://wiki.tinycorelinux.com/tiki-index.php?page=Integrating_extensions

This would depend on which extensions are installed, and vary with different computers. In one test I did, it took 45 seconds longer.

I think if extensions were integrated into a remaster, this time delay would not occur, or not be as great.

It may be worthwhile coming up with a method of integrating extensions into a remaster.

[Guy]

In any case as a newcomer to linux it isn't that I "fear the command line", no it is simply lack of knowledge of the thousands(?) of commands, each with their switches that take years to master.

There are some things that I have learnt how to do, and are not problem for me. However, I know new users would have difficulty with some of the more difficult things. I think it is important to keep things as easy as possible for new users. If people find it too difficult, they will use other operating systems. The easier it is, the more people will use Tiny Core.

[Jason W]

On more thought, having GUI or even dialog support means that one is going to have those extensions in the new iso whether they are desired or not.  Mkisofs-tools is the only one really needed, and I can add a flag to remove it from the new iso.  It will be command line but real simple.  Say for instance

mkiso.sh --backup --remove /mnt/hda1/tinycore-2.6.iso

--backup will include a backup and --remove will remove the mkisofs-tools extenison if the user does not want it included in the new iso. 

The first cd I made a year ago had the /tce directory on the cd, but /opt/tce is the supported location that will be used.

[danielibarnes]

RedB: A modification was made to rebuildfstab for Tiny Core 2.7 rc1. Please try it and let me know if it fixes your problem. The /etc/fstab file is essential to correct operation of the tce= boot parameter and the autoscan function. I suspect that /etc/fstab was not committed to the filesystem before your /tce directory was processed.

[Jason W]

Guy,
I did recently use /tce as the extension directory on a CD, and it does boot fast and use very little RAM.  Of course, /tmp/tce must be manually set in /opt/.tce_dir to load more extensions on the fly.  When /opt/tce is used, /tmp/tce is automatically set as the tce dir if no existing tce directories are either specified or scanned. 

A cd with /tce used as the tce directory will not integrate with existing tce directories, and an /opt/tce cd will as it was designed to be complementary to the main tce directory rather than being the main one. 

Only one of my machines boots from usb, so I do find running from a CD iso of interest.  I view using /tce kind of like using PPI.  It has it's advantages in certain circumstances for older machines but at the expense of being compatible with all of TC's modes and concepts.  One can use /tce as the directory if they understand the limitations.  But for general use on most machines /opt/tce is recommended.

[Guy]

I haven't tested it, but I suspect making a remaster using /opt/tce would boot faster than using opt_tce.gz.

[Jason W]

Perhaps, though the initrd files are loaded one after the other, so unzipping a 10mb one followed by a 30mb one may or may not have a noticeable difference from unzipping a 40mb one.  My personal preference would be to keep available the option of "base norestore" use of the cd, but remasters by definition are tailored to personal preference.  Too bad initrd's cannot be loaded after a persistent /opt is set up to accomodate older hardware while keeping the dynamic features of using /opt/tce.  But if persistent media is present, there are the other running modes available.