Steve, ls bozo ... Was that an implication?? :-) I knew about stdin, stderr etc, just didn't know how to apply them thanks!
BTW, I never said programmers were #*@#&, just that I don't claim to be a &^%# programmer! Thanks!! Barry deFreese NTS Technology Services Manager Nike Team Sports (949)-616-4005 [EMAIL PROTECTED] "Technology doesn't make you less stupid; it just makes you stupid faster." Jerry Gregoire - Former CIO at Dell -----Original Message----- From: Steve Juranich [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 4:40 PM To: deFreese, Barry Cc: 'nate'; [EMAIL PROTECTED] Subject: Re: Why do I need to be a %^#$# programmer to use Linux? > OK, stupid n00b question coming. How can I capture the screen output in my > terminal to a file so I can show you the errors that I am getting? I tried > outputting or piping to a file and it doesn't work. Is there some way for > me to capture the screen output to a file?? ( You know in winblows, I can > just cut and paste!! :-) ) If you're running bash, you can redirect the error output (stderr, in %^#$#'ing programmer speak) by typing '2>filename' after your command. Example: quail (ss)$ ls bozo 2>errors quail (ss)$ cat errors ls: bozo: No such file or directory quail (ss)$ HTH -------------------------------------------------------------------------- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washington http://ssli.ee.washington.edu/ssli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
