Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6106 - Installer and filesystem labels

Attached to Project: Arch Linux
Opened by Victor (Victor) - Saturday, 30 December 2006, 11:56 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 18 July 2008, 15:41 GMT
Task Type Feature Request
Category Installation
Status Closed
Assigned To Simo Leone (neotuli)
Aaron Griffin (phrakture)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I think it will be nice if we include and option in the installer to add a label for each filesystem. Then we could use persistent block device naming for solving hdX->sdX problems (http://wiki.archlinux.org/index.php/Persistent_block_device_naming).
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 18 July 2008, 15:41 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Installer uses UUIDs. Anyone is free to replace this with labels at install time
Comment by Roman Kyrylych (Romashka) - Monday, 01 January 2007, 23:15 GMT
Hm, I'm sure I saw somewhere that one user reported about problems with LABELed root and grub.
Comment by Pierce Lopez (ploxiln) - Tuesday, 02 January 2007, 02:55 GMT
I think it's possible that some user thought that grub could perhaps use the labels instead of (hdx,y), which of course isn't the case. I haven't had a problem passing root=/dev/disk/by-label/archroot as the kernel parameter in grub's config (and only referring to labels in fstab), not anywhere referring to an hdx/sdx, using a mix of ide/pata/sata devices under both i686 and x86_64 arch.
Comment by Roman Kyrylych (Romashka) - Tuesday, 02 January 2007, 09:59 GMT
Yes, that issue was exactly the same as you dascribed. :)
Comment by Damjan Georgievski (damjan) - Saturday, 17 February 2007, 02:46 GMT
+1 on using LABEL's instead of device names.

I've had that setup for some time and never had problems. I also switched from ide_piix to ata_piix driver when I upgraded to 2.6.20, and I didn't have to touch any settings.

BTW I also use suspend2, so at one time vol_id didn't recognize the label of the swap partition because suspend2 flags it. But brain0 patched vol_id, so that's no longer a problem.
Comment by Michal Krenek (Mikos) - Friday, 18 May 2007, 10:33 GMT
There is one problem - you can't change label of already existing FAT filesystem with dosfstools (you can only specify label while creating FAT filesystem with mkdosfs -n <label> <other options>). But as I said in task #6201, there are mtools (in extra repository) which can do it:

mtools can be used very easily for changing labels of FAT filesystems. But you must first set disk mapping in mtools configuration file (I didn't find option to make it on command line... but maybe there is some hidden one?). So we can do for example this (if you want to change label of /dev/sda7 to "new_label"):

echo 'drive c: file="/dev/sda7"' > /tmp/mtools.conf
MTOOLSRC=/tmp/mtools.conf mlabel c:new_label
Comment by Gavin Bisesi (Daenyth) - Friday, 25 April 2008, 19:50 GMT
What's the status of this bug?
Comment by Glenn Matthys (RedShift) - Friday, 18 July 2008, 12:53 GMT
The installer uses UUID's now. (Which is, imo, a bad thing). If you want to use another naming scheme, modify menu.lst or fstab yourself, the installer won't conflict with that.

Loading...