Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If you run a command in a terminal, "standard output" is the terminal---ie it displays on the screen. If you have a file named "stdout", how big is it? Does it have ANY data?
To purposely put the output of fsck into a file:
fsck /dev/sda8 >filename 2>&1 (this sends (re-directs) stdout to filename, and sends stderr to the same place)
Note that there is actually a file called "stdout". It's in /dev and is a special device file.
Any text sent into this file gets printed on your shell's stdout (terminal typically).
"cat /dev/stdout" doesn't do much good, since "cat" will try to read from a device that's normally used for writing (ie writing to your terminal window) only.
Note that there is actually a file called "stdout". It's in /dev and is a special device file.
Any text sent into this file gets printed on your shell's stdout (terminal typically).
"cat /dev/stdout" doesn't do much good, since "cat" will try to read from a device that's normally used for writing (ie writing to your terminal window) only.
Aha!!!!
If that is the file he was looking at, it all makes sense. OP--where are you??
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.