On Wed, 2003-08-27 at 13:05, Mark Hounschell wrote:
zentara wrote:
On Wed, 27 Aug 2003 12:28:57 -0400 Mark Hounschell <dmarkh@cfl.rr.com> wrote:
I have a file -rw-r--r-- 1 root root 149811 2003-08-07 17:49 xx
As a regular user I edit the file. Make some changes and write it back. Now the file is -rw-r--r-- 1 markh users 149811 2003-08-27 12:23 xx
Am I missing something? Why was I able to write the file? Why was its owner and project changed from root to the users? Do the directory permissions override the file permissions? I must be missing something????
A user can COPY and edit and save a file owned by root, but the result is a file owned by the user. You didn't change root's file. You made a copy owned by you.
I must still be missing something. It is in fact the same file. It was owned by root now it is owned by markh?? I made no copy. It is the same file.
Doesn't -rw-r--r-- 1 root root 149811 2003-08-07 17:49 xx mean it is owned by root?
??? Mark
What editor are you using? I bet it does something like: read orig file into ram edit ram copy rename orig file *.old create new file delete *.old One way to tell is to look at the inode number, not the filename. ls -i will give you the inode number. See if it changes or is the same before and after the edit. If it does work like I describe above, the only real fix is to set the permissions on the directory. Directory permissions control things like delete and rename. Greg -- Greg Freemyer