WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: sda/ as backup device and empty bootlocal.sh  (Read 2183 times)

Offline alu

  • Sr. Member
  • ****
  • Posts: 429
sda/ as backup device and empty bootlocal.sh
« on: April 21, 2009, 03:58:40 AM »
i usually use tc on a usb drive in order to be able to work on several machines. lastly, i used tc on a hp laptop which recognize the pendrive as /dev/sdc* instead of /dev/sda* (as it has been usually recognize on my own AAO laptop).

I booted tc on the hp laptop with usual cheatcodes and let it search for my backup. It did. I worked with tc on the hp laptop, and then shutdown the system without making a backup (which was not useful).

I got back to my AA0, pluged the pendrive and run tc on it, and i noticed the following issues:

1. my backup device is sda2; /opt/.backup_device shows now sda/

2. my bootlocal.sh is empty; i had a command for my keymap in it.

Offline tobiaus

  • Suspended
  • Hero Member
  • *****
  • Posts: 599
Re: sda/ as backup device and empty bootlocal.sh
« Reply #1 on: April 23, 2009, 09:54:21 AM »
this is exactly what uuid's are for. they're a new feature, someone will have to tell you how to get the uuid.

the uuid is especially useful if you want to boot automatically from the same code on every machine. if you're typing in the device manually at boot, you'll probably still prefer the usual /dev/name system, only because it's less to remember and type.

Offline alu

  • Sr. Member
  • ****
  • Posts: 429
Re: sda/ as backup device and empty bootlocal.sh
« Reply #2 on: April 24, 2009, 03:17:44 AM »
thanks, but yes, i prefer remaining with the old system for the moment; even if i shall try the new one