l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
January 6: Social gathering
Next Installfest:
TBD
Latest News:
Nov. 18: Club officer elections
Page last updated:
2003 Jun 09 10:30

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Shell Scripting Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Shell Scripting Question



richard,

ever since i learned perl a year or two ago, i literally haven't touched
shell scripting other than reading other people's scripts, so i'm a bit
rusty, however, i think bourne style conditionals have the form:

if [ condition ]
then
do something
fi

or:

if test condition
then
do something
fi


afaik, perl/php C-style conditional's aren't part of bash's syntax.

references:

o'reilly's bash shell scripting is an excellent, excellent reference.

the only thing which rivals it is wiley's "unix shell programming" which
has the benefit of showing you how to do it in bourne style scripting
and csh style (for those who are unfortunate enough to be stuck in csh
for some ungodly reason).

also, kernighan and pike's "unix programming environment" is my favorite
(ironically, i may have this title wrong because i loaned my copy to a
friend) and is what i learned bourne scripting from.

the last two references are very good, but don't include bashisms, like
the string handling stuff that's so powerful.  however, i've found that
"man bash" is great for people who know bourne but don't know bash.
conversely, i wouldn't want to actually learn basic bourne scripting
from the man page.

the 1st and 3rd references are available from nerdbooks.  not sure about
the 2nd.

if i got something wrong, i'm sure someone will mention it.  :-)

hth,
pete



On Fri 06 Jun 03, 10:28 AM, Richard Crawford <rscrawford@mossroot.com> said:
> I have a script to chmod all of the files of a given name to 777, no
> matter where they lie in the directory tree:
> 
> 
> ################################################
> 
> find . -name $1 -print | while read i do
>   chmod 777 $i
>   echo "Modified: $i"
> done
> 
> ################################################
> 
> Now what I need it to do is to go into only those directories called
> "messages" and do the same thing to files in those directories.  I tried
> passing "messages/*" to $1 but, of course, that didn't work.  I've also
> tried adding a conditional, "if (grep "\/messages\/" $i)", to the script,
> but that, of course, didn't work either.
> 
> I've Googled for various scripting tutorials, but none of them seem to
> cover this particular issue, which is kind of time-sensitive.
> 
> Any suggestions would be greatly appreciated!

-- 
GPG Instructions: http://www.dirac.org/linux/gpg
GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.