Here is a twofold question, with a theoretical part, and a practical one:
I have been studying the Linux kernel behaviour for quite some time now, and it’s always been clear to me that:
Say I am writing my own init program running on a Linux kernel.
I have a remote machine running Debian 8 (Jessie) with lightdm installed. I want it to start in no-GUI mode, but I don’t want to remove all X-related stuff to still be able to run it though SSH with the -X parameter. So how to disable X server autostart without removing it?
Installing a new system using a GPT partitioned disk dedicated to a single partition, ext4 formatted, extlinux (version 4.05) as bootloader, Ubuntu Core version 13.10 amd64 as rootfs, and Ubuntu linux-image-3.11.0-18-generic as kernel, and extlinux-update to generate bootloader configuration.
I start a new process from GNOME Terminal and then this process fork a child.
But when I killed the parent process the orphaned process’s parent id became something other than 1 which represent init --user pid.
When I do this in virtual terminals, the parent pid is 1 which represent init process.
How can I execute new process from GNOME Terminal so that when it is died, the child process’s parent pid became 1 and not pid of init --user process?
Thanks a lot.
I need one process run before log in to system. How to run it like services? how do I make services in Linux?
I was going through a tutorial on setting up a custom initramfs where it states:
The init process exists as an ancestor of all of processes on a linux system. Does this process have any kind of IPC entry point ? Do other processes ever do IPC with init for any reason ?