On 2014-01-12 19:57 (GMT-0800) Linda Walsh composed:
LABEL's are only understood by linux -- so first you have to boot a linux to read the labels -- I found that out the "hard way" when I had to boot to 'S' and there were no labels...
This is a Linux mailing list, right? I see Windows, and various utilities and applications show me volume labels. What point are you trying to get across?
Not only no disk labels but the stuff I thought I'd put in the boot disks wasn't available because it was booting off a ram disk. I couldn't figure out a way to put my test code into the early boot sequence to see what was happening (was trying to setup *optional* console redirection to a serial port) -- so I reverted to boot from hard disk and haven't looked back.
Does any of the above paragraph have anything to do with anything previously written in this thread, the OP in particular?
I've mostly stopped using labels because something has to already be up to populate /dev/disk/by-*/ (i.e. the kernel needs to be booted and udev has to already have been called in the "boot" phase (i.e. /etc/boot.d/(scripts))... Only after the boot phase has done its stuff are "higher level" things like labels available.
If you're not using labels, what are you using, and why? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org