On 07/25/2012 02:25 AM, Juan Antonio Pedreira Martos wrote:
> I think it should be explained somewhere in the LFS book, as an
> optional feature, the possibility of assigning labels to partitions.
>
> I've recently finished my first LFS build under a virtualbox vm with
> success. I used two virtual disks: one for the host system and another
> for LFS. At first I did not used the grub loader installed in the LFS
> partition, as the host's "update-grub" found the LFS system and
> everything worked right.
>
> But as a final step, I wanted to get rid of all coupling with the host
> system by removing the host drive. And then I bumped into the real
> problem: the drive names have changed (i.e. sdb -> sda) and my
> /etc/fstab was consequently wrong. I did some research to change the
> default behavior and I found that the labels were the solution.
>
> As I think I am not the only one wanting to do this, here is what I
> think it should be included in the book:
>
> The label of an "normal" partition [at least, my ext3 partition used
> to mount "/"] can be set with:
>     e2label /dev/sdaX LFS_ROOT
>
> The label of a swap partition can be set when creating it [I don't
> know if it can be set after]:
>     mkswap -L LFS_SWAP /dev/sdaY
>
> To check what has been done, just execute:
>     blkid
>
> And finally, to make fstab label-dependant, edit /etc/fstab and
> replace /dev/sdaX (and /dev/sdaY) with LABEL=LFS_ROOT (and
> LABEL=LFS_SWAP).
>
> Also, to use Grub with labels [I haven't tested it yet]:
> http://ubuntuforums.org/showpost.php?p=9585951&postcount=13
>

I prefer UUID=... It is always available, it is tied to ONE partition 
and it is UNIQUE. No need to label anything. Just run "blkid" and you'll 
get UUID's for all of your partitions. But ... You can't use neither 
UUID nor LABEL in grub unless you use initramfs. I have been using UUID 
in my fstab for a long time and never had any problems.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to