Comments for /dev/movabletripe

Comment on I got 99 problems but a bitch ain’t one! by annual business travel insurance

annual business travel insurance — Thu, 03 Jul 2008 04:00:42 +0000

annual business travel insurance…

beaded frightfully albacore accommodates emphasize Faulkner …

Comment on Recursively chmod directories only by Garçon aka Martin Kopta » Blog Archive » links for 2008-06-07

Garçon aka Martin Kopta » Blog Archive » links for 2008-06-07 — Sat, 07 Jun 2008 23:33:41 +0000

[...] /dev/movabletripe » Recursively chmod directories only Recursively chmod directories only June 19th, 2006 find . -type d -exec chmod 755 {} ; This will recursively search your directory tree (starting at dir ‘dot’) and chmod 755 all directories only. Similarly, the following will chmod all files only (tags: commandline chmod) [...]

Comment on Recursively chmod directories only by Charles

Charles — Mon, 07 Apr 2008 18:56:21 +0000

Take not to do something silly when mass changing files. I untarred a tarball, and blithely (blindly!) changed files to 644. Of course I needed many configure files to be executable. They weren’t. the build broke. Silly me!

Otherwise, this is what I needed.

Comment on I got 99 problems but a bitch ain’t one! by Adam

Adam — Sun, 06 Apr 2008 06:50:39 +0000

Well, I did spend too little time and too much scotch on this. Of course grep bitch myproblems.txt is a better way of doing it. Old (bad) habits die hard.

However, as far as I can tell, cat is needed for wc, as it outputs the filename as well. Of course, I could be wrong, but wc(1) doesn’t seem to have an option to supress the output of the filename. You could always wc -l myproblems.txt | awk '{print $1}' but it serves the same purpose essentially.

Comment on Recursively chmod directories only by Daniel

Daniel — Sat, 05 Apr 2008 22:27:05 +0000

Awesome! Thanks for the tip, exactly what I was looking for.

Comment on I got 99 problems but a bitch ain’t one! by tehdely

tehdely — Tue, 01 Apr 2008 22:30:10 +0000

Useless use of cat.

Comment on Recursively chmod directories only by Justin

Justin — Thu, 27 Mar 2008 20:29:25 +0000

Another helpful command for changing files of only a specific type/extension is:

find ./ -name *.pdf -exec chmod 755 {} \;

Comment on Recursively chmod directories only by Allen Halsey

Allen Halsey — Thu, 20 Mar 2008 20:28:54 +0000

Thanks for the tip! Reading the man page for chmod, I came across another tip for recursive chmod. I often encounter the situation where the ‘user-owner’ permissions are correct, but the ‘other’ permissions have been made too restrictive, disallowing read access. The following command will fix it:

chmod -R o+rX .

Note that the capital ‘X’ causes it to do the right thing regarding the executable bit: directories will be executable and files will be made executable only if the file is executable for the ‘user-owner’ or ‘group-owner’. Check out the man page for chmod.

BTW, I always like to say ‘user-owner’, ‘group-owner’, and ‘other’, to help me keep straight that ‘u’ is for ‘user-owner’ and ‘o’ is for ‘other’.

Comment on Recursively chmod directories only by Yep!

Yep! — Mon, 10 Mar 2008 20:46:37 +0000

Perfect, it solved my problem instantly!

Comment on Recursively chmod directories only by thehenrys.net » Recursively chmod directories or files only

thehenrys.net » Recursively chmod directories or files only — Wed, 20 Feb 2008 16:54:02 +0000

[...] http://movabletripe.com/archive/recursively-chmod-directories-only/ [...]