News for hackers. Stuff that matters.
Re:The Beauty of Unix Pipelines by asdff on Thursday June 04, 2020 @08:45PM (#23423813)
whats a simple example of using this?
Re:The Beauty of Unix Pipelines by gorgoiler on Friday June 05, 2020 @12:37AM (#23425126)
It’s how all new processes in Unix are created. There is no “spawn new process running this code” operation. Instead:

(1) you duplicate yourself with fork()

(2) the parent process continues about its business

(3) the created process calls execve() to become something else

This is the mechanism by which all new processes are created, from init (process 1) to anything you run from your shell.

Real life examples here, in this example of a Unix shell:

https://github.com/mirror/busybox/blob/master/shell/ash.c

Re:The Beauty of Unix Pipelines by Icathian on Friday June 05, 2020 @09:19AM (#23428142)
Bash is probably the best example of this style of working. You have a shell process that forks and spawns child processes from itself that are turned into whatever program you've called from your terminal.
Re:The Beauty of Unix Pipelines by zwetan on Saturday June 06, 2020 @01:51AM (#23437131)
see here: https://pubs.opengroup.org/onlinepubs/9699919799/functions/e...

plenty of basic examples with execv, execve, execvp, etc.

if the execv() call succeed then it completely replaces the program running in the process that calls it

you can do plenty of tricks with that ;)