Results 1 to 1 of 1
I'm programming a custom-built Linux OS using the 2.6 kernel.
My question, while simple in my mind but is apparently complex since searching Google and this very forum for hours ...
- 01-26-2011 #1Just Joined!
- Join Date
- Mar 2010
- Posts
- 5
Setup TTYs at boot...
I'm programming a custom-built Linux OS using the 2.6 kernel.
My question, while simple in my mind but is apparently complex since searching Google and this very forum for hours has yielded no results, is "how to you enforce the TTYs to be setup at boot, first?"
The boot process goes to init, then executes the /etc/sysinit file. The /etc/inittab looks like:
This is a very simple toaster box, however, the problem is that if there is a hang in the sysinit file for any reason, no other TTYs are accessible until the /etc/sysinit file has fully completed it's execution.Code:# Setup the TTYs first so that we have a terminal to access in the event # that the sysinit hangs for any reason. tty1::respawn:/etc/run_admin tty2::respawn:/sbin/console tty3::respawn:/etc/login.py tty4::respawn:/etc/login.py tty5::respawn:/etc/login.py # System Initialization ::sysinit:/etc/sysinit # Shutdown ::shutdown:/bin/umount -a -r # Trap when CTRL-ALT-DELETE gets pressed ::ctrlaltdel:/sbin/reboot
Is there any way to fully setup all five TTYs prior to the /etc/sysinit or am I just mis-understanding the simple order of operations for the Linux boot process?
Any help would be greatly appreciated!


Reply With Quote