Timeline for Understanding piped commands in Unix/Linux
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 22, 2019 at 17:15 | history | edited | G-Man Says 'Reinstate Monica' | CC BY-SA 4.0 | Pipes have nothing to do with GNU, except for the fact that the shell supports pipelines, and shells did this long before bash existed; also, the question has nothing to do with C. Tweaked formatting and wording; restored some of OP’s wording; changed tags. |
| Apr 22, 2019 at 1:30 | comment | added | Sergiy Kolodyazhnyy | @炸鱼 You're correct - for kernel pipeline is an object in pipefs filesystem, but as far as shell itself is concerned - technically that's a pipeline command | |
| Apr 22, 2019 at 0:45 | comment | added | 炸鱼薯条德里克 | It's not command, it's an kenerl object created by bash process, which is used as stdout of process A and stdin as B. Two processes are started nearly at the same time. | |
| S Apr 21, 2019 at 23:16 | history | suggested | S.S. Anne | CC BY-SA 4.0 | Formatting, proper capitalization |
| Apr 21, 2019 at 22:38 | answer | added | Sergiy Kolodyazhnyy | timeline score: 2 | |
| Apr 21, 2019 at 21:35 | comment | added | G-Man Says 'Reinstate Monica' | Related: In what order do piped commands run? | |
| Apr 21, 2019 at 21:01 | review | Suggested edits | |||
| S Apr 21, 2019 at 23:16 | |||||
| Apr 21, 2019 at 21:00 | history | tweeted | twitter.com/StackUnix/status/1120069893536321537 | ||
| Apr 21, 2019 at 13:14 | history | edited | ctrl-alt-delor | CC BY-SA 4.0 | fix grammar, punctuation, reduce verbosity, and better title |
| Apr 21, 2019 at 12:52 | history | became hot network question | |||
| Apr 21, 2019 at 12:34 | vote | accept | nihulus | ||
| Apr 21, 2019 at 12:26 | answer | added | Kusalananda♦ | timeline score: 27 | |
| Apr 21, 2019 at 12:00 | review | First posts | |||
| Apr 21, 2019 at 13:10 | |||||
| Apr 21, 2019 at 11:59 | history | asked | nihulus | CC BY-SA 4.0 |