Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
However, the above command also alters the flags for directories; I want to avoid changing the attributes of the directories.
(The reason I'm doing this is that Rox-Filer generates thumbnails only for image files that do not have executable bits set; therefore I wish to chmod my pics folder tree, and remove the executable bits from all image files. If I remove the executable bits from folders, however, I can no longer open them.)
I don't really know - find just requires it for its syntax. It marks the end of arguments to whatever is exec'ed. As guesses, possibly since you're issuing two commands, in a sense, you need both the semi-colon as a 'line separator' and a newline. The first tells find you're done with chmod and the second tells bash you're done with find. Or, going another way, the semi-colon lets find tell chmod its done when find execs it. The '{}' is substituted with filenames by find and the ';' actually tells chmod it can execute. Maybe the command is actually 'chmod file1 ; chmod file2 ; chmod file 3...' with the semi-colon being inserted on each file that returns 0 from the type test when 'chmod file1 chmod file2' would be an error. (The backslash is just escaping the semi-colon, of course.) Last shot is that it's just some kind of getopt() requirement. It'd take seeing (and understanding) the source code to really say, I guess. Somebody who can do that should be able to say for sure.
Oooo!!! this find stuff is exciting! My life has been horrible since I had all my music on an NTFS partition before I bailed on Windows, and everthing was executable, and I did a chmod -r to unexecutable them, and fuckit if I could see inside directories anymore.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.