On Friday 29 of January 2010 18:11:53 Henry Hung wrote:
> Hi
> I don't know whether this is a design intent or a bug.
> When I tried to list recursively a specified file, ls only searched the
> current directory for the file, not recursively. For example, ls -R myFile*
http://www.gnu.org/software/
Hi
I don't know whether this is a design intent or a bug.
When I tried to list recursively a specified file, ls only searched the current
directory for the file, not recursively. For example,
ls -R myFile*
displays only files with myFile pattern residing in the current working
directory but not
Hi Jim,
It looks the "Modify chmod" task has been in TODO list for a long time.
I have looked through the discussion thread referred to
http://bugs.debian.org/497514.
Does it make sense to make chmod do not change the inode's ctime
if the new permission bits is identical to the old as the defaul