WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Boot parameters tce, cde, and restore/norestore - change the name of /tce?  (Read 130 times)

Offline cparke

  • Newbie
  • *
  • Posts: 19
Initial questions:
  • I am unclear what is the difference between tce= and restore= ?
  • It seems like 'norestore' does not stop the search for a /tce directory?
  • What does 'cde' actually do?  It too does not seem to stop the search for a /tce directory
At issue is I have placed a /tce backup directory on one of my hard drive partitions, and I can't stop any TinyCore CD/USB/ISO boot from using it! (other than by using the 'base' boot option, but then I get nothing off the CD image)

The problem is my /tce directory has extension binaries for TinyCorePure64-16.0, but if I want to boot from CD a different version of TinyCore on the same machine (for example, CorePlus-12.0-32bit), the system still reads the /tce and tries to load the 64-bit extensions into the 32-bit kernel, which is a disaster! 

I really thought 'cde' and/or 'norestore' would bypass the search for /tce, or wish there was some way to specify another name for the /tce directory to search for (like tce=sda1/tce64-16.0), but it seems like it has to be '/tce' and you can only have one backup directory per device?

Apologies if this question has been asked before 100 times, 'tce' is a very common search term and I really can't digest all the hit results from over the 15+ years.

Thank you.
« Last Edit: April 06, 2025, 05:30:31 PM by cparke »

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12009
Hi cparke
tce=  Tells Tinycore where to look for the tce directory.
restore=  Tells Tinycore where to look for mydata.tgz (it defaults to the tce directory).
norestore  Tells Tinycore not to restore the files you backed up.
cde  Tells Tinycore you are booting from read only media (CD).

Try adding a boot code to a bogus tce location, for example:
Code: [Select]
tce=sda9

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12009
Hi cparke
If that doesn't work, rename the onboot.lst file in the tce directory
it's trying to load extensions from. If it doesn't find onboot.lst, it
won't try to load anything from there.

Offline cparke

  • Newbie
  • *
  • Posts: 19
I studied the /usr/bin/tce-setup script and how it processes the tce= boot parameter.

It turns out, using tce=sda1/tce64-16.0 as the boot parameter actually works perfectly!


Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12009
Hi cparke
Yes, moving the tce directory was another option. Tinycore
will only auto scan root directories of partitions for /tce/.

Offline cparke

  • Newbie
  • *
  • Posts: 19
Yes, but what I'm also saying is the tce-setup shell script that you wrote about 15 years ago also already supports reading from the renamed directory, which is the best solution.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12009
Hi cparke
Yes, I know. I guess I didn't spell it out in my previous reply.

It's also mention in the FAQ:
Quote
tce=UUID="12345_678/tinycore/tce" for normal installation.
Found here:
http://tinycorelinux.net/faq.html#pendrives