[ale] New Trick (was: Baffled on chmod usage)

[Jeff Hubbs]

 OK, looks like I have to do one more thing - many of the file and directory
names contain spaces, which is making the chmod command crap out when it
hits them in the find output.  Any suggestions on how to frame the path/file
names in quotes?  I'm working on some kind of double-pipe...

- Jeff

> -----Original Message-----
> From: Jeff Hubbs [mailto:Jhubbs at niit.com]
> Sent: Thursday, August 10, 2000 4:26 PM
> To: ale at ale.org
> Subject: [ale] Baffled on chmod usage
> 
> 
> I want to chmod all the .exe files within and below the 
> directory "public,"
> so I go:
> 
> 	# cd /<path>/public
> 	# chmod -Rv 555 *.exe
> 
> but I get
> 
> 	chmod: *.exe: No such file or directory
> 
> FWIW, there are no .exe files in public, but there are many of them
> scattered in directories underneath public.  What I especially don't
> understand is that if I go 
> 
> 	# chmod -Rv 555 *
> 
> then everything and its brother in public and below gets 
> chmodded.  I can
> use some other extension besides .exe that I know is present 
> but I still get
> No such file or directory.
> 
> Am I misusing wildcards in bash or something?
> 
> - Jeff
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" 
> in message body.
> 
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.