Subject: Re: Recursive grep (where is limfree defined?)
To: Don Lewis <email@example.com>
From: Missing - presumed fed. <greywolf@defender.VAS.viewlogic.com>
Date: 01/24/1996 10:41:27
#define AUTHOR "firstname.lastname@example.org (Don Lewis)"
* On Jan 23, 1:15am, email@example.com wrote:
* } Subject: Re: Recursive grep (where is limfree defined?)
* } I don't think a recursive grep is any worse than a recursive chown or
* } chmod. You can accomplish all three with using 'find xargs', but it is more
* } convenient to let the command take care of it.
* IMHO recursive chmod is worthless. In general I don't want the same
* permission bits on files and directories.
Unless, of course, you use -R [ugo][+-=]X (sets all execute bits IFF
the file is executable at all, or it's a directory). I've had cause
to use this one quite often. Also, for my home directory:
chmod u=rwX,g=rX,o=X ~
#undef AUTHOR /* "firstname.lastname@example.org (Don Lewis)" */
Assignment: Think about and expound upon the possibilities of these two
questions. What would the world be like today if
a) the Roman Empire had been defeated early on? (religious implications)
b) the Stock Market had not crashed? (economical/political implications)