Seeing that /dev/null's utility isn't immediately obvious to me, what is the use of /dev/null piping?
-
8Your current user handle.Ketan– Ketan2014-02-10 05:08:59 +00:00Commented Feb 10, 2014 at 5:08
-
Read the wikipedia page on it: en.wikipedia.org/wiki//dev/null. But given your username I'm going to assume you already know what it does and are goofing w/ us.slm– slm ♦2014-02-10 05:15:11 +00:00Commented Feb 10, 2014 at 5:15
-
3This question appears to be off-topic because it appears to be a joke.slm– slm ♦2014-02-10 05:15:56 +00:00Commented Feb 10, 2014 at 5:15
-
It wasn't. You're just not creative.Suppressing Output– Suppressing Output2014-02-10 06:07:16 +00:00Commented Feb 10, 2014 at 6:07
-
You are newbie, read this PDF: sourceforge.net/projects/linuxcommand/files/TLCL/13.07/…Sepahrad Salour– Sepahrad Salour2014-02-10 06:10:47 +00:00Commented Feb 10, 2014 at 6:10
|
Show 4 more comments
2 Answers
make >/dev/null
this will send the normal output to nowhere land, and retain all the errors right in front of you on the screen. Anything basically you don't need to see/have fill your screen you send to /dev/null
/dev/null is used where input, output, or both are not necessary. A read will result in zero bytes being returned. A write will accept any amount of data, and simply discard it.
This is most useful for cron jobs where you don't care about the output (or input, as the commands will not be running on an interactive terminal) Or where you want only the exit status of a command without any output.
