Mike my next question is besides my learning the basics of of 'find' 'locate' more grep?' I am very happy you responded thank you for caring enough to take your time to help. By the way the 'find' command is able to delete files marked on date and time as well as locate files within a certain folder 'allowing correct permissions'.

 Erik are you saying that the command $ rsync  <source> <dest> is better than say # cp -r <source> <dest>

> From: tclug-list-request at mn-linux.org
> Subject: tclug-list Digest, Vol 101, Issue 6
> To: tclug-list at mn-linux.org
> Date: Thu, 9 May 2013 00:43:37 -0500
> 
> Send tclug-list mailing list submissions to
> 	tclug-list at mn-linux.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mailman.mn-linux.org/mailman/listinfo/tclug-list
> or, via email, send a message with subject or body 'help' to
> 	tclug-list-request at mn-linux.org
> 
> You can reach the person managing the list at
> 	tclug-list-owner at mn-linux.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tclug-list digest..."
> 
> 
> Today's Topics:
> 
>    1. find command (Mike Miller)
>    2. Re: find command (Erik Anderson)
>    3. Re: Ubuntu 13.04 to be supported for only 9 months (Mike Miller)
>    4. Re: find command (Mike Miller)
>    5. Re: find command (Michael Moore)
>    6. Re: find command (Erik Anderson)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 9 May 2013 00:16:18 -0500 (CDT)
> From: Mike Miller <mbmiller+l at gmail.com>
> To: TCLUG Mailing List <tclug-list at mn-linux.org>
> Subject: [tclug-list] find command
> Message-ID: <alpine.DEB.2.00.1305082345540.18074 at taxa.psych.umn.edu>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
> 
> On Thu, 25 Apr 2013, Paul graf wrote:
> 
> > I would like to study the 'man find' command with another person 's who 
> > are interested in the command. Finding files that have been modified and 
> > sent to folders on a certain date in time. The 'find' command is very 
> > powerful I believe. I would enjoy a workshop and to listen and be able 
> > to talk with others 'such as yourself'. I am sorry to not send my 
> > message clearly I have no formal education.
> 
> First -- for finding files on the system, it is often a lot faster and 
> easier to use "locate".  Check that out.  I usually capture the output 
> from locate using less because sometimes there are a lot more lines than 
> you would think because every path that includes a string will be show.
> 
> locate whatever | less
> 
> Then I'll use grep commands to limit the results:
> 
> locate -i whatever | grep -i tclug | less
> 
> The -i option makes the command case insensitive.
> 
> 
> Here is something cool and useful that I do with find.  Suppose I have a 
> directory "foo" and that has a directory tree inside it with thousands of 
> files.  I want to copy it to some other machine, remote_host, and after it 
> arrives, I want to check that it's all there and unchanged.  First I use 
> find with md5sum to make a file of md5 hashes:
> 
> find foo -type f -print0 | xargs -0 md5sum > foo_md5sums.txt &
> 
> The "-type f" option causes find to list only regular files, then 
> "-print0" uses null characters instead of newlines to delimit the files in 
> the output list, but xargs with "-0" option takes that kind of list as 
> input.  The reason for using the nulls instead of newlines is that it 
> allows xargs to handle properly filenames with spaces.  Next I transfer 
> the file:
> 
> scp -rp foo foo_md5sums.txt remote_host:.
> 
> That's using scp, but there are other ways one might copy files across a 
> network, or you might even use an external drive, flash drive or DVD to 
> send files somewhere.  Then go to the other machine...
> 
> ssh -X remote_host
> 
> ...and run this check:
> 
> md5sum --check foo_md5sums.txt | grep -v OK$
> 
> The --check option uses the md5sums file as input and checks every file 
> listed, which includes every file in the foo directory tree.  The grep 
> command at the end is just deleting all the lines that say the file was 
> OK.  If a file was not present or it didn't match, you will see some 
> output.
> 
> Mike
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 9 May 2013 00:25:39 -0500
> From: Erik Anderson <erikerik at gmail.com>
> To: TCLUG Mailing List <tclug-list at mn-linux.org>
> Subject: Re: [tclug-list] find command
> Message-ID:
> 	<CADdM08o53cDV-X9v=0yA9b+ZB1D=5aV95-4uNYdXfHvS9j=OVg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> On Thu, May 9, 2013 at 12:16 AM, Mike Miller <mbmiller+l at gmail.com> wrote:
> 
> > Here is something cool and useful that I do with find.  Suppose I have a
> > directory "foo" and that has a directory tree inside it with thousands of
> > files.  I want to copy it to some other machine, remote_host, and after it
> > arrives, I want to check that it's all there and unchanged.
> 
> 
> $ rsync  <source> <dest>
> 
> Will do essentially the same thing, minus all the manifest file
> rigamarole...
> 
> -Erik

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20130509/ff32506a/attachment.html>