modify chmod
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 default behavior? I'd like to handle it if it is still a valid task and nobody is working on for now. Regards, -Jeff
(no subject)
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 those in the sub-directories. All I want to do is to look for files with certain pattern throughout all sub-directories and the paths those files are located. ls -R | grep myFile* works great but it doesn't give me the path of those files. Is there a easy way to do it? Thanks Henry __ Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
Re: (no subject)
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/coreutils/faq/coreutils-faq.html#Why-doesn_0027t-rm-_002dr-_002a_002epattern-recurse-like-it-should_003f Kamil
