WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: What are Proper Boot Codes for 2.10 TCE/Install Mount Mode?  (Read 2307 times)

Offline reidi

  • Newbie
  • *
  • Posts: 13
What are Proper Boot Codes for 2.10 TCE/Install Mount Mode?
« on: March 27, 2010, 08:06:01 PM »
I've just upgraded from 2.7 to 2.10 (started over from scratch actually), and I don't remember the UUID boot parameter being in 2.7.  What are the proper boot codes so that my USB stick install will be recognized if booted from multiple machines?  This is what I have, and it works at least on one machine, but it looks wrong to me - tce is defined twice:

quiet host=Aries waitusb=5 max_loop=255 tce=UUID="blah_blah_blah" tce=LABEL=tinycore home=LABEL=tinycore opt=LABEL=tinycore restore=LABEL=tinycore

I use tune2fs to set LABEL like so: tune2fs -L tinycore /dev/sda1

Any suggestions?


Offline ^thehatsrule^

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 1726
Re: What are Proper Boot Codes for 2.10 TCE/Install Mount Mode?
« Reply #1 on: March 27, 2010, 08:11:22 PM »
You can stick with using LABEL by removing the UUID parts.

Or if you want to use UUID, then get rid of the LABEL parts and use something like `blkid /dev/something` to get the id.

Offline reidi

  • Newbie
  • *
  • Posts: 13
Re: What are Proper Boot Codes for 2.10 TCE/Install Mount Mode?
« Reply #2 on: March 27, 2010, 11:00:51 PM »
You can stick with using LABEL by removing the UUID parts.

Or if you want to use UUID, then get rid of the LABEL parts and use something like `blkid /dev/something` to get the id.

So, do I need only the tce=UUID="[output from blkid]" ?

Or do I also need something to define home, opt and restore?  What would that look like, please?  "home=UUID=tinycore"?

Offline reidi

  • Newbie
  • *
  • Posts: 13
Re: What are Proper Boot Codes for 2.10 TCE/Install Mount Mode?
« Reply #3 on: March 27, 2010, 11:05:38 PM »
You can stick with using LABEL by removing the UUID parts.

Or if you want to use UUID, then get rid of the LABEL parts and use something like `blkid /dev/something` to get the id.

Okay, I see it in the FAQ.  THanks.