Making TC persistant

[sam0010]

I have installed TC to a harddrive partition using the installation guide. It boots but any application I install is not persistent.  It seem as if I need to set a boot code but when I try to load boot codes at the boot prompt I get:  IO APIC RESOURCES COULD NOT BE ALLOCATED.  I would appreciate if someone would help me make my applications persistent.  Thanks.

[JoXo009]

I have installed TC to a harddrive partition using the installation guide  ...

If your install is not persistent it's sure that
you didn't really follow the installation guide.

It's not easy to do more than 20 steps without a single typo. Newcomers often have to try two to three times till they succeed.

Fastest way to solve your problem: Do the install again.

----
If you want to invest time in understanding the background, you have to be aware that TC stores its extensions in the tce directory.

On boot TC autoscans for that directory and creates a new (non persistent, temporary) one if no tce dir is found.

To be persistent the tce dir needs to be living on a storage device like a hard drive.

If your hard drive partition is mounted to
/mnt/hda1
open a root terminal and enter the command
mkdir -p /mnt/hda1/tce
reboot and extensions will be permanent.

If your harddrive partition has got a different name
change 'hda1' correspondingly.

---------
By the way, using TC may be easier to learn when installed as guest system within a virtual machine like Sun's Virtual Box.

Than you don't risk to be cut off by any error, as you always can go back to your previous snapshot.

[sam0010]

Thanks.  I got it to be persistent.

[Pats]

Looking at so many threads on TCL persistancy - I think users are hell-bent on making TCL permenent persistant , while the TCL developers time and again explained abt TCLs cloud mode multiple uses and its core policy.
How abt it ?
~ Pats

[thane]

Persistency is easy to get. It was a little obscure the first time(s) I tried, but it's actually very simple. And I do occasionally boot into cloud mode when I want to try an app without adding it to a set of extensions. I like the flexibility and extreme customization features of TCL.

The thing about Linux is that if you don't like a particular distro's design philosophy (or anything else), there are a lot of other distros to choose from. And it's all free. I'll complain and/or ask for help if TCL claims to be able to do something and I can't get it to work. But if TCL wasn't basically what I wanted I'd look around for something else.

[Pats]

Not only persistancy, but the whole concept of TCL is very easy - once one get accostmed to TCL philosphy ! For example, even though I am using linux for a while, I was confused abt TCL different uses and file locations, only after 10 practical sessions I was able to properly customize TCL as per my needs.
And I think some users who venture into LINUX world right from TCL, must be tearing off their hairs in intro sessions to TCL.

And to add more confusion ( at least when I had started using TCL ), TCL wiki was of not much help that time. I hope the wiki is with its improved version. But one thing is damn sure , all the Linux users must try their hand on TCL at least once, then only one get addicted to TCL use, cause there is so much to experiment & improve TCL. It is really exciting !
~ Pats