{"id":1872,"date":"2020-09-18T16:55:00","date_gmt":"2020-09-18T13:55:00","guid":{"rendered":"https:\/\/www.virtono.com\/community\/?p=1872"},"modified":"2020-09-16T15:12:28","modified_gmt":"2020-09-16T12:12:28","slug":"using-redirection-to-read-and-write-data-from-anywhere-in-the-linux-terminal","status":"publish","type":"post","link":"https:\/\/www.virtono.com\/community\/knowledgebase\/using-redirection-to-read-and-write-data-from-anywhere-in-the-linux-terminal\/","title":{"rendered":"Using redirection to Read and Write data from anywhere in the Linux terminal"},"content":{"rendered":"\n

Redirection of results and input is an all-natural function of any development or scripting language. Technically, it happens whenever you connect to a computer inherently. Input gets to go through from stdin (standard input, generally your keyboard or mouse), the output would go to stdout (standard output, a text message or data stream), and errors get delivered to stderr. Knowing that these data streams can be found enables you to regulate where information goes if you are using a shell, such as for example Zsh or Bash.<\/p>\n\n\n\n

You should get your feet wet by using these tutorials and getting to know linux better on a Cloud VPS from here<\/a>.<\/p>\n\n\n\n

Standard in, standard out, and standard error exist as filesystem locations on Linux. You can see them in \/dev<\/code>:<\/p>\n\n\n\n

$ ls \/dev\/std*<\/strong>
\/dev\/stderr@  \/dev\/stdin@  \/dev\/stdout@<\/strong><\/gwmw><\/p><\/blockquote>\n\n\n\n

You can’t carry out much with them directly, but it’s sometimes beneficial to think about them as meta-locations where one can send data.<\/p>\n\n\n\n

The fundamentals of redirection are simple: use some number of > characters to redirect output, plus some true number of < characters to redirect input.<\/p>\n\n\n\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n