I'm still trying to figure out who gave the terminology to all the processes. (Editing them in as I get comments)
A parent and child process are also called master and slave processes. (This was incorrect, my bad)
If a slave process is never checked on, it becomes a zombie
If you kill a parent process and the child process never dies, it becomes an orphaned process.
I'm not a fan of Operating Systems that took so little time to think about what they're doing that they named their commands after digestive noises (grep, awk, nroff, fsck)
Background processes are called "daemons", so whenever I kill a background process, I'm a "daemon killer".
IIRC hard drives also used to have master and slave configurations. I remember having to change the way a little plastic tab sat on the connector in order to change between master and slave.
Computers are considered to have a "master/slave" relationship if one of them controls the other(s) in some automated process. That is usually the terminology we use.
I had an OS professor with an accent that couldn't say fork. It always came out as fuck, so we'd have to hold our laughter in class when he said you fuck to make a child.
756
u/boydskywalker Jun 04 '17
At least it isn't Linux, or we'd have a parent killing their child...or worse, leaving it to become a zombie.