A project for UNIX/Linux by QUINTON CLARK during the FALL 2011.

This project was begun on 12/8/11 and is anticipated to take 5-10 MINUTES.

To find out if the program mystery outputs to STDOUT or STDERR.

In order to successfully accomplish/perform this project, the listed resources/experiences need to be consulted/achieved:

• tty
• cd
• file
• ./

I want to see where the program mystery outputs to, if it is STDOUT.

I hope to find an output to the program.

State and justify the attributes you'd like to receive upon successful approval and completion of this project.

• attribute1: why you feel your pursuit of this project will gain you this attribute
• attribute2: why you feel your pursuit of this project will gain you this attribute
• etc…

The actual steps taken to accomplish the project. Include images, code snippets, command-line excerpts; whatever is useful for intuitively communicating important information for accomplishing the project.

lab46: /var/public/unix/eoce$ ./mystery 
Hello, this is the program you have to run.
To where is my output going??? Figure it out.
lab46: /var/public/unix/eoce$ file mystery 
mystery: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped
lab46: /var/public/unix/eoce$ tty
/dev/pts/34

When you run a program and it outputs data then you know that it outputs from somewhere and can tty it and find where its being outputted from. Otherwise if you get an error message, it's just an error message.

In performing this project, the following resources were referenced:

• My brains
• Classmates help