Re: can touch(1) readonly files
But how can I protect _myself_ from _myself_?
I seem to recall in past UNIXes things weren't this "bad".
uid=1000(jidanni) gid=1000(jidanni) ...
$ chmod -w -R ee
$ find ee|xargs touch -d 'next year'
$ find ee|xargs ls -ld
dr-xr-xr-x 3 jidanni jidanni 1024 2004-05-13 16:43 ee
-r--r--r-- 1 jidanni jidanni 0 2004-05-13 16:43 ee/ff
dr-xr-xr-x 2 jidanni jidanni 1024 2004-05-13 16:43 ee/gg
I mean I can understand why access times still should be changed, but
where is the logic in allowing modification times to be changed?
Again, I ask, as a regular user, why can't I protect _myself_ from
_myself_ changing file modification times? I wonder just how many of
the times in the inode are now gullible.
$ uname -a
Linux debian 2.4.20-k7 #1 Tue Jan 14 00:29:06 EST 2003 i686 unknown unknown GNU/Linux