windows visible only under root

alagenchev · 02-09-2005, 07:57 PM

OK, I changed my /etc/fstab , so that it will mount windows at startup:

/dev/hda3 swap swap defaults 0 0
/dev/hda2 / reiserfs defaults 1 1

/dev/hda1 /windows vfat auto 0 0

/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0

I also did chmod 777 /dev/hda1

everything looks fine , but when I am not inder root I cannot access /windows

I checked: ls -l /
and for /windows I have rwxr--r--

I tried chmod 777 /windows

but there's no result, it is like the command doesn't work and I cannot access my windows under regular user. I am running Slack 10. I used to have RH 7.3, 9.0 FC3.0 and SuSE 9.1 and did not have any problems. What do I need to fix? Anyone, please help.

Bruce Hill · 02-09-2005, 08:10 PM

Quote:

Originally posted by alagenchev
OK, I changed my /etc/fstab , so that it will mount windows at startup:

/dev/hda3 swap swap defaults 0 0
/dev/hda2 / reiserfs defaults 1 1

/dev/hda1 /windows vfat auto 0 0

you must add the flag user after auto ->

Code:

/dev/hda1        /windows         vfat       auto,user             0   0

alagenchev · 02-09-2005, 08:35 PM

Sorry, it did not work. Any other suggestions?

Bruce Hill · 02-09-2005, 09:33 PM

Yes. Copy mine and change what is relevant to your box

Code:

mingdao@james:~/titus$ cat /etc/fstab
/dev/hda5        swap             swap        defaults         0   0
/dev/sda1        /                reiserfs    defaults         1   1
/dev/sda2        /home            reiserfs    defaults         1   2
#/dev/sda3        /usr             reiserfs    defaults         1   2
#/dev/sda5        /var             reiserfs    defaults         1   2
#/dev/sda6        /tmp             reiserfs    defaults         1   2
/dev/sda7        /distro          reiserfs    defaults         1   2
/dev/cdrom       /mnt/cdrom       iso9660     noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
/dev/hdb         /mnt/dvd         iso9660     noauto,user,ro   0   0
/dev/hdc         /mnt/cdrw        iso9660     noauto,user,ro   0   0
/dev/hda1        /XP              ntfs        user,umask=1000,ro,auto      1   0  <- Windoze partition read-only 
/dev/hda2        /PROGRAMS        ntfs        user,umask=1000,ro,auto      1   0  <- Windoze partition read-only 
/dev/hda3        /DATA            vfat        user,umask=1000,rw,auto      1   0  <- Windoze partition read-write 
###added these for usb devices
/dev/sdb1        /mnt/sdb1        vfat        user,umask=1000,rw,noauto    0   0
/dev/sdc1        /mnt/sdc1        vfat        user,umask=1000,rw,noauto    0   0
/dev/sdd1        /mnt/sdd1        vfat        user,umask=1000,rw,noauto    0   0

I got 3 Slackware boxen with dual-boot setups and they all work...

You may have to restart something to make it work. Since I don't
know what to restart, just reboot Slack...

alagenchev · 02-09-2005, 10:27 PM

Thanks a lot, this is great.

what does the umask=1000 thingy do?

Bruce Hill · 02-09-2005, 10:49 PM

Quote:

Originally posted by alagenchev
Thanks a lot, this is great.

what does the umask=1000 thingy do?

In a terminal issue and read
$ man umask

That is the way someone told me to set it up when I ran
Debian, and so I've always used the 1000 flag. However,
when I read "man umask" I didn't understand the 1000 or
read anything to do with it.

I've been using 1000 for about 2 years. We now have 5
Slackware boxen in this house, 3 with dual-boot systems,
and it's never caused a problem. However, like you, I would
like to know what the 1000 means.

I hope you can now read/write or whatever you desired
from your vfat partition. I guess you do understand that
runnning Windoze, you can't see your Linux partitions, so
that vfat should be the one where you share data between
the two systems.

alagenchev · 02-09-2005, 11:28 PM

he he I guess I can help too.

OK I opened

an old UNIX book I have and refreshed my memory a little bit. umask is a utility that will set permissions for new files or directories. So it is kind of like chmod but before the files are created. The big difference between umask and chmod is that umask is like wildcard i.e. if you have all 000 you are not denying any permitions and the result will be 777 , which is rwxrwxrwx 777 restricts all permissions 4- restricts r only, granting w and x. So the correct syntax in fstab is actually 000 not 1000 . The one has no effect. I already changed my fstab, restarted and it really has no effect. I guess that's it. Thank you for the help and also this was a great reason to brush up on some commands.

P.S. Yes, I knew about the fact that I cannot see my Linux partition under Windows. Thanks anyways.

Bruce Hill · 02-09-2005, 11:32 PM

Thanks for your explanation. I never read in "man umask"
that it didn't do anything, but should realize that from the
silence. I'll change my /etc/fstab entries accordingly. ;-)