Inittab file store the information of

Runlevel 6 is reboot. I have a "regular" desktop pc. Questions: If I'll add another getty line, once linux startup I will see two separate terminals?

Improve this question. Add a comment. Active Oldest Votes. Question 1: Yes, by adding more getty lines you can get more terminals in parallel. If using a serial port, the openvt command will not apply. Question 3: There is more to initializing a TTY session for a particular non-root user than just starting a shell with su.

Question 4: Yes, you can. Improve this answer. From my understanding - if I can see it inside the terminal there must be a getty who opened this first terminal for me.

I guess the ttys0 getty is the one opened this first stty for me. Stephen Kitt Stephen Kitt k 45 45 gold badges silver badges bronze badges. Can I ask for a smail clarification regards sec. Done, see the update. Now the getty will run a different command , every command that I'll choose , and will not call to the system login process as before The key is getting getty to open the TTY for you; its normal behaviour is to wait for a login name, then run login , connected to the TTY; login waits for the password, checks it and starts the shell, also connected to the TTY.

For example if I want to skip the login phase - to be able to open my system with root user without entering any user name or password. Show 5 more comments. Because of xx But your inittab looks simple and correct - only the last comment, and the "z6" entry Sign up or log in Sign up using Google. They differ from run levels in that the init command can never enter run level a , b , or c. Also, a request for the execution of any of these processes does not change the current run level.

Furthermore, a process started by an a , b , or c command is not killed when the init command changes levels. The getty command writes over the output of any commands that appear before it in the inittab file. To record the output of these commands to the boot log, pipe their output to the alog -tboot command.

The stdin, stdout and stdferr file descriptors may not be available while init is processing inittab entries. To display the record for cdrom, enter: lsitab "cdrom" The output is similar to: cdromrespawn:startsrc —s cdromd.

The telinit command initializes and controls processes. For a description of the other action keywords, see inittab 4. The following example shows an annotated default inittab file that is installed with the Solaris release:. Executes any process entries that have sysinit in the action field so that any special initializations can take place before users login.

Executes any process entries that have a 3 in the rstate field, which matches the default run level, 3. For a detailed description of how the init process uses the inittab file, see init 1M. Viewed 18k times. Improve this question. How about calling that script in rc. As by the time rc. Would doing this be as simple as pasting the script given in the readme of NoIP into rc.

It says "does nothing" because there's nothing in it to do it's all yours. But don't paste the whole script in, because whatever happens there should exit ASAP -- generally by forking to create a new background process which can run as long as it likes. I think I understand. So even though the script's only function is to start NoIP upon system startup, if you don't fork the NoIP process, when the script finishes running the NoIP process would be killed?

There's nothing it it because all the logic has moved to systemd files. And if you don't fork the NoIP thing, the boot process would have to wait this is annoying, not harmful. Add a comment. Active Oldest Votes. Quick Background The current version of Raspbian is 8, aka. The problem is that there doesn't appear to be any such directory Inittab wasn't a directory, it was a file.

Hence the first version of Raspbian was 7, not 1.