Persistence? (remastering)

[_blue4meridian]

I'm fairly new to Tiny Core.  I do not understand and/or know the boot codes and the location of the file to be edited.  I downloaded the 3x repository and can only do a temporary install.  Many thanx for all suggestions.

[removed exe links]

[tinypoodle]

http://forum.tinycorelinux.net/index.php?topic=7495.0

[_blue4meridian]

I have read these topics (and they have helped greatly in other areas) but on this topic I do not fully understand it as posted.  I have bookmarked several topics that suggest the solution (cheat and/or boot codes) but have not fully grasped the specific location of the file to be edited or the correct syntax for persistence.  Basically, I am somewhat confused as I am lacking a laymans description.  Again, many thanx...

[removed exe links]

[tinypoodle]

boot codes have to be specified either in config file or at prompt of (if there is such a latter) of whatever bootloader is used

[_blue4meridian]

I see... However, I'm still not quite clear on the name and location of the config file and syntax entry.  Anyway... thanx for all the info so far.  I believe I will eventully be on the right page with the procedure.  I installed Tiny Core with unetbootin (@http://webwarper.net/ww/unetbootin.sourceforge.net/) to a usb fat partition if that is any help.

[removed exe links]

[tinypoodle]

That's why I was not more specific; exact syntax and config paths/files would differ between specific bootloaders and setups.

(personally I wouldn't happen to have any idea of unetbootin)

[_blue4meridian]

Did some research... unetbootin does not seem to support persistence.  However, Portable Linux (@http://webwarper.net/ww/rudd-o.com/new-projects/portablelinux) does.  I could solve the problem this way or I could edit the .ISO with isomaster.  In the case of the former (using Portable Linux)... Tiny Core Live Cd (.ISO) would have to support "Casper" (however, I would still have to figure out the "config").  For the latter (using unetbootin)... would it be as simple as copying the /tce folder to the root of the Tiny Core .ISO file before installation?  All input on this thread is a lifesaver... thank you.

[removed exe links]

[tinypoodle]

As you appear a bit lost about where to start with to achieve persistence, allow me to make a suggestion to simplify things and take them step by step:

1. Boot from CD where bootloader is already installed and configured, and just add your own options at prompt upon each boot. This of course would require that the hardware available supports booting from CD.

2. Achieve persistence of dynamical (personal) data, using the TC feature of backup/restore.

3. Optionally achieve persistence of statical data (extensions) with a PPR.

All that is required is some storage space on a FAT* or ext* partition.

[_blue4meridian]

Unfortunately, I only have a netbook (no disk drive just .ISOs) and I'm shooting for portability (USB stick) so I'm not really sure I can do it with unetbootin/isomaster or Portable Linux.  Still in all thanx again...

[removed exe links]

[gutmensch]

Unetbootin uses syslinux to create a bootable linux filesystem. After you ran it for your usb key (assuming it is FAT on your key), browse it and create a folder structure tce/optional/. Put into optional all your desired extensions. Create a file called onboot.lst in tce/, which contains your extensions to load on startup.

Example (this is linux like, if you have windows, then create dirs and files within windows explorer, download the extensions in a browser, etc.):

Code: [Select]

cd /media/USB
mkdir -p tce/optional
cd tce
echo kmaps.tcz > onboot.lst
cd optional
wget http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/kmaps.tcz
wget http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/kmaps.tcz.md5.txt

Touch your backup file:

Code: [Select]

cd /media/USB
touch mydata.tgz

Open the file /media/USB/syslinux.cfg. Edit the tinycore entry. Example:

Code: [Select]

label ubnentry0
menu label tinycore
kernel /boot/bzImage
append initrd=/boot/tinycore.gz quiet

After or before quiet you can add boot codes. Example for a changed line:

Code: [Select]

append initrd=/boot/tinycore.gz quiet waitusb=6 tce=sda1 restore=sda1

Waitusb is necessary because usb devices need some time to be initialized on startup. The entries are assuming (sda1) that your usb key will be recognized by tinycore as the first scsi/usb/sata disk in the system. If you have other drives you may need to change it to /dev/sdb1 or /dev/sdc1, ...

Save your syslinux.cfg and plug the key in, boot from it. Take a look after a boot if the kmaps extension was loaded (must be present in /tmp/tcloop).

[_blue4meridian]

Ah, I see... What should I do as an alternative if I decide to use isomaster to change the .ISO to get persistence... simply add the /tce/optional folder to the root of the .ISO? The info to date has helped greatly... thanx.

[tinypoodle]

Why remaster the .iso after stating that you can't boot from an optical drive?

[_blue4meridian]

As an additional optional approach (just in case I get access to a disk drive and/or as an easier alternative) I was interested in the possiblity of editing the .ISO then doing a unetbootin install. Although the /tce would be permanent (at least until the next .ISO edit)  I suppose the remaster (using isomaster) would be dual purpose (install/live) one.  Thanx for all the feedback.

[gerald_clark]

tce needs to be writeable.
ISOs are not writeable.

[tinypoodle]

That could be helped by placing extensions into /opt/tce/optional, in which case then the default /tmp/tce will be used as tce_dir.