On Fri, Aug 03, 2007 at 11:17:21PM -0400, Phill Atwood wrote: > > > > Success. Although I can't say that I really understand. Setting > umask=0222 in the /etc/fstab file did the trick. I don't understand why > mounting a ro partition to a directory with just write permissions would > work. 0544 or 0555 seemed the more logical thing to try... its a mask so you turn on the bits you want off in the final result. if one digit of your mask is 2 then it looks like: 010 that makes the final perm is 5 and it looks like: 101 if the mask is 0 : 000 then perm is 7 or : 111 so a mask of 5: 101 becomes perm 2: 010 and not what you want. So I'm not sure how that translates to the first digit since i'm sure you don't want a perm to come out 7555 using umask of 0222 but maybe someone can enlighten > > As a relative newby here are some things I noted that I don't get. > > a) Previously, I made a group and added my users to it, editted fstab to > allow gid for that group, chmoded the directory to 0544 and set the > umask in fstab to be 0544 too. This almost worked. I was able to cd to > my windoze directory, but I couldn ls -l it! I don't remember how it works. 0544 gives you perms of 0255 or -w-r-xr-x so the owner can't ls it as you can neither read nor execute, but I'm surprised you could cd to it too... its confusing, i know. > > b) When I created my new group bar and added my user foo to it with > "adduser foo bar" it worked. When I issued the "groups" command it did > not show bar as being one of the groups that foo belonged to. I > rebooted, issued "groups" again and now foo is in bar. Seems to me it > should know this right away without a reboot... (I'm showing my Windoze > ancestry by rebooting all the time!) you get your groups at login. Until you log out and log back in, you won't get new groups. You don't need to reboot, just log out everywhere and log back in. > > c) Even after this success, dmesg shows: > > NTFS volume version 3.1. > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume > flags 0x4000 encountered. > NTFS-fs error (device sda1): load_system_files(): Volume has unsupported > flags set. Mounting read-only. Run chkdsk and mount in Windows. i see that a lot and never have any problems. FWIW. but avoid writing in ntfs if you can. ... > > Another thing: If you also need write access onto ntfs, and want read access onto compressed files, then the ntfs-3g driver might be interesting for you. For newbies however, it might not be that easy to install... you need to make a package for stable yourself. On the other hand, if you'd need it, I can just do an update/recompile here on my system and send the resulting package to you via email. is it in backports? A
Attachment:
signature.asc
Description: Digital signature