When a system starts up, the kernel initiates a few of its own activities as processes and launches a program called init
init, in turn, runs a series of shell scripts (located in /etc) called init scripts
The fact that a program can launch other programs is expressed in the process scheme as a parent process producing a child process
# to look at process ps# to show all process regardless of terminalpsx# output PIDTTYSTATTIMECOMMAND1876?Ss0:02/usr/lib/systemd/systemd--user1881?S0:00 (sd-pam)1895?Ss0:12/usr/bin/appimagelauncherd1902?Sl0:00/usr/bin/gnome-keyring-daemon--daemon1915tty2Ssl+0:00/usr/libexec/gdm-wayland-session/usr/1917?Ss0:00/usr/bin/dbus-broker-launch--scopeus1920?S0:02dbus-broker--log4--controller9--m1923tty2Sl+0:00/usr/libexec/gnome-session-binary1982?Ssl0:00/usr/libexec/gnome-session-ctl--monit1983?Ssl0:00/usr/libexec/uresourced--user1986?Ssl0:00/usr/libexec/gnome-session-binary--sy1990?Ssl0:00/usr/libexec/gvfsd# for a detailed lookpsaux# outputUSERPID%CPU%MEMVSZRSSTTYSTATSTARTTIMECOMMANDroot10.00.217332817748?Ss16:290:01/usr/lib/systemd/systemdroot20.00.000?S16:290:00 [kthreadd]root30.00.000?I<16:290:00 [rcu_gp]root40.00.000?I<16:290:00 [rcu_par_gp]root50.00.000?I<16:290:00 [netns]root70.00.000?I<16:290:00 [kworker/0:0H-events_highpri]root90.00.000?I<16:290:00 [kworker/0:1H-events_highpri]root100.00.000?I<16:290:00 [mm_percpu_wq]root110.00.000?I16:290:06 [kworker/u32:1-blkcg_punt_bio]root120.00.000?I16:290:00 [rcu_tasks_kthread]root130.00.000?I16:290:00 [rcu_tasks_rude_kthread]root140.00.000?I16:290:00 [rcu_tasks_trace_kthread]root150.00.000?S16:290:00 [ksoftirqd/0]