oakeny wrote:
> On Wed, 6 Mar 2013 15:58:40 PST, eldiener wrote:
>
> > TeraByte Support wrote:
> >> You need to have the use volume label option enabled, they show for
> >> fat/fat32/ntfs file systems. If the Extended partition is properly
> laid
> >> out
> >> then yes they would be in the same order. You can use edit file to look
> at
> >>
> >> what files are on the partitions, then label them if not
> fat/fat32/ntfs.
> >>
> >> "eldiener" wrote in message news:
4865@public.bootitbm...
> >>
> >> If I click on Volumes within an extended partition in order to hide one,
>
> >> there is no indication which volume is which in the extended partition.
>
> >> Since all my logical volumes in my extended partitons have labels, it
> would
> >>
> >> be real nice if BootItBM would identify each logical volume by its
> label.
> >> This cannot be too difficult to do.
> >>
> >> Given that BBM does not show the logical volume label, can it be assumed
>
> >> that BBM is showing the volumes in the order that they occur in the
> >> partition table ? So that, let's say, if I see in Linux that my extended
>
> >> partitions are sda5, sda6, sda7 etc. this is the order in which BBM is
> >> showing them ?
> >
> > These are Linux partitions, all with a disk label for each partition. Why
> is it so hard to pick up the disk label for a Linux partition as opposed to
> a fat/ntfs partition ?
> >
> > I think BIBM should automatically read the labels for disk partitions and
> show them so that it becomes easier for the end-user to identify each
> partition, most notable extended logical partitions. All of the
> partitioning software I know of is able to do that. Given how generally
> excellent I feel BIBM is in its basic functionality and flexibility it is a
> bit disappointing that such functionality is not implemented in BIBM.
> >
> > I am glad nevertheless that the partitions are shown in the same order
> that I would see them in GParted, ie. in partition table order.
> >
> > Thanks for your help !
>
> What I have done on occasions in the past with BING is to create a text
> file in the root of each partition with a descriptive name (eg !WinXP-40G)
> so that I can click the Edit File button, look at the top of the list of
> files (hence the ! character at the start of the text file name), and
> check
> the identity of the partition.
>
> Maybe this would be a useful backstop for your purposes too?
There should be no necessity for this for this sort of kludge. BIBM should certainly be capable of reading disk labels and showing them for every partition. Why such an otherwise excellent software program is not doing this is something I do not really understand. Name a software partitioner program and I am sure it shows the disk labels very clearly to the end-user. At least every one I have ever used does this, including GParted. It is not as if the disk label for a partition is somehow an obscure feature. I know that using a UUID has gained greater use in the Linux world and I use UUIds myself internally in my Linux distros in 'fstab' and 'grub/grub2', but I also make sure every partition, whether a primary MBR, logical volume MBR, or GPT, has a disk label for easy visual identification in programs which show/manipulate partitions.
I do hope the Terabyte programmers add the feature to BIBM to display disk labels for all partitions both when working with partitions and when looking at the different partitons when editing a boot item. I makes it much easier to identify partitions that way.