LinuxQuestions.org - HDD Order in 'Computer'

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - HDD Order in 'Computer' (https://www.linuxquestions.org/questions/linux-general-1/hdd-order-in-computer-313683/)

HDD Order in 'Computer'

I finally just decided instead of dealing with NTFS or ext3 as a documents hard drive just to settle for FAT32. Since I couldn't format a 250gig drive and have it work in Windows, I split it into two 125s.

Anyway, I did fstab and everything (can someone tell me what the commands unmask=???? ? ? does?), but there is a slight annoyance. I named the drives Caviar A and Caviar B in Windows (how do you do this in Linux? because for some reason, linux is making these all caps, but my 32gig raptor is in proper caps!?). It mounts the second partition first, and then the first partition, so in 'Computer' I have...

125G Hard Drive: CAVIAR B
and
125G Hard Drive (2): CAVIAR A

I'd much rather the first one be A, and the second B, and also name it so that they aren't all caps. 'Raptor' is proper caps though, and I did it the exact same way. If possible, I'd like to remove the (2) also. I know all of this is cosmetic but its really weird because it's hard enough having some things on one drive and some things on another, but having them in differing orders is kind of crazy.

PS I tried switching the order in fstab.

Can you post your fstab so we can give you real world examples?

A generic idea:

/dev/hda1 is Caviar A in Windows. In Linux, it set it up arbitrarily to /dev/hdb1 as Caviar A. You want /dev/hda1 as Caviar A and need to tell fstab so. Your current entry would look something like:
/dev/hdb1 "/mnt/Caviar A" vfat option1,option2,and,so,on 1 1

And you would modify it (not just the order):
/dev/hda1 "/mnt/caviar A" vfat option1,option2,and,so,on 1 1

Note the /dev difference.

As for what umask does:

One way to grant permissions on any given file or directory is to run the command chmod. Umask is the 'equivilent' (not really, but for simplicity we'll take that) of chmod, but using the opposite numbers. So, a chmod of 777 will grant the earth permission on that file, while a umask of 000 will do the same thing.
Not exactly a complete definition of umask, but a usable one ;) For more info you can always check out the docs on chmod and mount.

Cool

Code:

# This file is edited by fstab-sync - see 'man fstab-sync' for details

LABEL=/                /                      ext3    defaults            1 1

none                    /dev/pts                devpts  gid=5,mode=620      0 0

none                    /dev/shm                tmpfs  defaults            0 0

none                    /proc                  proc    defaults            0 0

none                    /sys                    sysfs  defaults            0 0

LABEL=SWAP-sda3        swap                    swap    defaults            0 0

/dev/hdd1              /mnt/caviara            vfat    auto,users,exec,rw,umask=000  0 0

/dev/hdd2              /mnt/caviarb            vfat    auto,users,exec,rw,umask=000  0 0

/dev/sda1              /mnt/windows            ntfs    auto,users,exec,ro,umask=0222 0 0

/dev/hdb                /media/cdrecorder      auto    pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0

/dev/hda                /media/cdrom            auto    pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0

I'm saying that the fstab appears correct, and it does mount them to the right folders, but in 'Computer' it has them in the opposite order than I would like. They are labelled correctly, but they consider A to be the 'second' one.

It also seems like I'm sometimes having problems with the drive under Linux. For instance, I try to rename a file by right click renaming, and it blinks for a second like you can type in it, then it goes back to as if I had never even tried to rename it. This only happens in 'list' view.