-=> ROY J. TELLASON wrote to WAYNE CHIRNSIDE <=-

 RJT> Wayne Chirnside wrote in a message to Charles Angelich:

 WC> Neato though now I need to read up on scripts to take that
 WC> and direct the output into a file.

 CA> AFAIK the same as DOS, "> " will redirect it to a file?

 WC> Tried that, didn't work, also tried >>.

 RJT> That's supposed to append.

I am aware but having tried > and failing what's to lose by trying?

 WC> It creates the file but nothing there.

 RJT> ...And > didn't?
                                         
Created a file and added but a single bit for each entry,
no text.

 RJT> You could try a pipe:  |

Dang, you know I've seen enough Linux syntax to have thought of
that but didn't, redirect and pipe it into the file that's the 
ticket!. Untried but intuition tells me this is correct.

 WC> I recall Ron at Abilities giving a very short script using grep
 WC> that searched the entire drive for a pattern in every file and
 WC> every directory. I may look for that disk on the off chance I
 WC> saved that to file, unlikely though that may be. This would be
 WC> very useful in both learning Linux _and_ figuring out how to fix
 WC> my SMTP authorization problem.

 RJT> If you have mc installed the search function in there will look for
 RJT> content, too.

I have mc installed however that short script, or actually as we had it
a command line input would very slickly search all 
partitions visable to Linux for a given character string and
pipe it into a file, you could use wildcards too.
I've got to break out the *nix book on scripts in *nix
I've got and do some serious studying.
MC can be a hinderence in the long run IMHO keeping you from
learning far more powerful tools.
I really hope I saved that script to disk and will have a looksee
in the next day or so and if not resort to that rather heavy
text on the subject. You know what's lacking in *nix, a few
led by the hand examples right off the bat before they get
into deep waters so you get the basic idea than run with it.
Learning scripting syntax is very high on my list of priorities.
Run a shell script to search for a string even using wildcards for a
incomplete character strings than redirect and
pipe that into a file and blink you're done.
If you're going to work at the command line time not spent learning
this early on is soon lost many times over in unnecessary
work as time moves forward.
Now I'm really new to this so bear that in mind but that's my thinking
on the matter.
--- Platinum Xpress/Win/WINServer v3.0pr5