I see now you have grub4dos on sda1, that changes the situation indeed.
To be absolutely safe you can use "LABEL" or "UUID",But what if I want to keep old setups such as that one I had on /dev/sda1. Is there no way to prevent menu.lst boot code stanza from seeing the 'wrong' live folder (the from= parameter maybe)? Otherwise, I imagine a lot of people could run into a similar problem.
from the porteus docs:
What Toni suggested is also fine of course:SPECIAL NOTE FOR USING CHEATCODES WITH 'LABEL' AND 'UUID':
If you specify a LABEL or UUID with a cheatcode, remember that all
portions of these commands are case sensitive. You should use a
unique label for each of your partitions if you wish to use device
labels with your cheatcodes. Use the 'blkid' command to view your
device's UUID and LABEL. Using UUID and LABEL can be quite handy
because they are unique to your device, and your data will be found
and properly mapped on different hardware configurations.
Every cheatcode which contains a /path can take advantage of 'UUID:'
and 'LABEL:' extensions.
Examples:
changes=UUID:STrING-0F-ChARACtERS/path/file.dat
extramod=LABEL:YourLabelName/path/to_folder/with_modules
from=UUID:STrING-0F-ChARACtERS/path/folder
rootcopy=LABEL:YourLabelName/path/to_folder/with_files
but still has a risk for folders with same name on different drives.Folder 'live' is inside folder 'debdog' (needs 'from' parameter):
Code:
title Live-port-dog from debdog (sda1/debdog)
root (hd0,0)
kernel /debdog/live/vmlinuz1 noauto copy2ram from=/debdog/ changes=/debdog/live/
initrd /debdog/live/initrd1.xz
Fred