On Wed, 30 Jan 2002, Bryan J. Smith wrote: > Bart Oldeman wrote: > > ~umask (bit-wise "not" of umask) is and'ed, not umask itself. > > So with umask=022 you turn off write permissions for group and > > user. > > umask=000 > > then it's world readable/writeable. That doesn't look very secure. > > If my /etc/fstab entry has umask=000 on the filesystem, what if my > user's umask=is 022. Do files get written by that user as 755 or > 777? I assume the former? If so, can I use ~umask=000 to force 777 > always?
It will be 777. Because all permissions on a FAT partition are the same. The exception are files with the FAT read-only attribute - those files will be 555 (r-xr-xr-x). If the user tries "chmod 755 file" the fs complains. > I'm going to be using a pre-2.4.10 kernel. As such, if my > /etc/fstab entry has noexec, the DOS programs will execute under > DOSEmu, but not under Linux, right? If so, I'd rather have it that > way. Yes, you will get this in Linux: gcc foo.c ./a.out bash: ./a.out: Permission denied on such a partition, post or pre 2.4.10 does not matter. But 2.4.10+ shows -rwxrwxrwx (777) a.out whereas older kernels show -rw-rw-rw- (666) a.out with umask=000. Bart - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
