Hi,
Looks like there is a problem with NFSv3 and file permissions in the DJ
kernels.
A file that is marked as executable will lose its executable flag whenever
it is written to. I suspect the proble lies in the changes to the NFS file
info cacheing in the DJ kernels at least since 2.5.20-dj1 (I was unable
to find where this change occured in the changelog).
Here is one example:
Enter NFS mount (in this case, the NFS server is a FreeBSD 4.6 machine)
Compile a simple program; gcc hello.c -o hello
Result: hello has the following permissions: -rw-r--r--
Modify the permissions manually; chmod 755 hello
Result: hello has the following permissions: -rwxr-xr-x
Here is another:
Enter NFS mount
Compile a simple program; gcc hello.c -o hello
Result: hello has the following permissions: -rw-r--r--
Unmount the NFS mount; umount /home
Remount the NFS mount; mount server:/home /home
Result: hello has the following permissions: -rwxr-xr-x
Here is the final one:
Enter NFS mount, find a file with executable permissions;
Edit a file; vi whahoo.sh
Save and close the file
Results: file has the following permissions: -rw-r--r--
So, in the process of writing a file, its executable bits are lost. Can
someone help? The problem is not present with vanilla Linux-2.5.20.
Regards,
- Brent Cook
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:32 EST