WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: What is the tclocal file/directory for?  (Read 3128 times)

Offline linus72

  • Full Member
  • ***
  • Posts: 196
  • Damn it Jim!
What is the tclocal file/directory for?
« on: May 19, 2009, 10:02:05 PM »
I don't understand it's use and there dowsn't seem to be any docs about it-so what is a tclocal file/directory and how is it used.
thanks

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: What is the tclocal file/directory for?
« Reply #1 on: May 20, 2009, 02:02:43 AM »
It is used to store extensions that are PPI compliant.
It is discussed in Core Concepts

The fourth mode of operation literally installs extensions into a Linux partition or a loop back file. This provides a hybrid type of installation, where core is in RAM and the extensions are installed onto a persistent storage device. I call this mode of operation of Persistent Personal Installation or PPI. The benefits are speed, as no loading or mounting occurs during boot. The same RAM savings offered by the mounted PPR/TCZ extensions is another benefit of PPI. However a possible drawback of this is losing the "pristine state" offered by using PPR. Installing applications, as done in most typical environments, can result in "system rot", i.e., over time, or via user/system error, corruption can occur and might not be readily noticeable. By choosing this method one should only use our TCE collection of extensions. The TCE collection being tar gzipped will install into the specified location. To initially setup your PPI use the boot code of local=hdXY. This will look for a directory named tclocal or a single loop back file of the same name. Note there is a menu option to create a loop back file for this very purpose. Using a PPI you don't need to keep the downloaded TCEs. No need to specify tce=hdXY as used in the PPR mode. For a "hands free" boot even the local=hdXY can be omitted. But by always specifying the local boot code will skip the autoscan and result in faster booting. Using the nolocal boot code will always ignore an existing PPI.
10+ Years Contributing to Linux Open Source Projects.

Offline mcewanw

  • Full Member
  • ***
  • Posts: 102
Re: What is the tclocal file/directory for?
« Reply #2 on: May 20, 2009, 02:56:15 AM »
The fourth mode of operation literally installs extensions into a Linux partition or a loop back file. This provides a hybrid type of installation, where core is in RAM and the extensions are installed onto a persistent storage device. I call this mode of operation of Persistent Personal Installation or PPI. The benefits are speed, as no loading or mounting occurs during boot. The same RAM savings offered by the mounted PPR/TCZ extensions is another benefit of PPI.

When using a loop back file for PPI, isn't that something like using one great big tcz? In which case is there any advantage (apart from less loop mounts) to using PPI in that way instead of PPR/TCZ?

Offline linus72

  • Full Member
  • ***
  • Posts: 196
  • Damn it Jim!
Re: What is the tclocal file/directory for?
« Reply #3 on: May 20, 2009, 05:48:05 AM »
OK-thanks, now, how do I get the tce extensions I already have into the the tclocal file or should I make the tclocal folder instead?