OK here is the auto start xserver stuff
patch to /etc/inittab:
That will leave c1 with the startup log, no login prompt, and borrow c6 to start an auto login. Now, I never understood why, but the startx there for me would always kick it off on c2, instead of c7 like it normally does. So you may or may have to leave c2 blank as well. I'm sure there is a way to control that...
/home/your_user_name/.bash_profile:
Again, that is not complete enough to deploy to others, but it might get you started. That if block there needs expanded, and probably a few more if blocks inside of that one - e.g. at the very least there should be a clean way to disable it if you know X is broken. And you may need an exit trap or some use of fork and wait. I'm not sure if that & after startx is right .. if I ever reboot my machine again I may revisit it.
Edited by lloyd mcclendon - 6/2/12 at 5:34pm
patch to /etc/inittab:
Code:
# TERMINALS
-c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux
+#c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux
+c1:12345:respawn:/bin/login -f your_user_name tty6 < /dev/tty6 > /dev/tty6
-c2:2345:respawn:/sbin/agetty --noclear 38400 tty2 linux
+#c2:2345:respawn:/sbin/agetty --noclear 38400 tty2 linux
c3:2345:respawn:/sbin/agetty --noclear 38400 tty3 linux
c4:2345:respawn:/sbin/agetty --noclear 38400 tty4 linux
c5:2345:respawn:/sbin/agetty --noclear 38400 tty5 linux
-c6:2345:respawn:/sbin/agetty --noclear 38400 tty6 linux
+#c6:2345:respawn:/sbin/agetty --noclear 38400 tty6 linux
That will leave c1 with the startup log, no login prompt, and borrow c6 to start an auto login. Now, I never understood why, but the startx there for me would always kick it off on c2, instead of c7 like it normally does. So you may or may have to leave c2 blank as well. I'm sure there is a way to control that...
/home/your_user_name/.bash_profile:
Code:
[[ -f ~/.bashrc ]] && . ~/.bashrc
if [ -z "${DISPLAY}" ] && [ $(tty) == /dev/tty6 ] ; then
startx &
fi
Again, that is not complete enough to deploy to others, but it might get you started. That if block there needs expanded, and probably a few more if blocks inside of that one - e.g. at the very least there should be a clean way to disable it if you know X is broken. And you may need an exit trap or some use of fork and wait. I'm not sure if that & after startx is right .. if I ever reboot my machine again I may revisit it.
Edited by lloyd mcclendon - 6/2/12 at 5:34pm
untitled
(30 items) |
|
untitled
(30 items) |
