In the following buffer copy, note that the file README
which exists in the backfs, is recreated with the wrong
permissions. It is recreated using the absolute umask value
rather than taking into account that README. as a non-directory,
should, therefore, be created without the execute bit set.
Note that the file 'nothing' which is not in the back file system,
is created with the proper permissions.
_______________
_______________
# ls -l README nothing
ls: nothing: No such file or directory
-rw-r--r-- 1 root root 988 May 30 1996 README
# rm -f README
# touch README nothing
# ls -l
total 1
-r-xr-x--- 1 root root 0 Sep 20 04:28 README
-rw-r--r-- 1 root root 920 Aug 8 2003 copyright
-r--r----- 1 root root 0 Sep 20 04:28 nothing
# umask
0227
#
---------------------
---------------------
There is a, vaguely related problem, in that -- if you have
not yet cached the inode for a file, you can write to it,
irrespective of permissions.. Thus, knowing that /etc/syslog.conf
exists, I can as thea non-root user (non-root) go:
echo *.debug /tmp/debug >> /etc/syslog.conf
directly after boot
At that point, the inode info is loaded, and I can
no longer write to the file.
I can, however, go:
chown knoppix /usr/share/doc/acl/README
and then take my time modifying the file.
--
Stephen Samuel +1(604)876-0426 [EMAIL PROTECTED]
http://www.bcgreen.com/~samuel/
Powerful committed communication. Transformation touching
the jewel within each person and bringing it to light.
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
