Hi

I have a question for how the file labels under the installation are
being determined. I had a problem with an error I made when installing
cooker - which I have done recently say 10 times because of other
problems. I may describe this in another mail.

One of the times I forgot to deselect my /var partition from mdk 9.1,
that is, because there was a /var label on that partition, the
installation partitioning suggested that I mounted that partition on
/var - and yes, then my rpm database for MDK 9.1 was gone... :-(

I then tried to figure our how to change the file system labels,
but till now to no avail. I tried e2label and  reiserfstune -l
but these did not change the labels that are used in drakx,
and mount -l did not show these labels. When using e2label, the new
labels did not show up in drakx either.

Can somebody tell me how to set these mounting point labels?

I like to use them. I have something like 30 partitions on different
harddisks on my development system, and file system labelling looks
a good way to keep track of them and it is also a good way of saving
time for setting up partitioning for installing different systems, and
even avoid errors like the above (and other similar or even more
disastrous errors:-(

If you make any changes, then please make something that would work also
for RedHat, Suse etc. My take is that it would  be better to use both
labelling schemes, (the one available with e2label reiserfstune etc, and
the apparant other scheme), with a preference to one of them. 
I also note that the labels seem to be restricted to 16 characters, which
is somewhat short, if this is a mount path. 

Best regards
Keld

Reply via email to