[Michelle Verkuyl] > This occurs regardless of whether I use the default getty > configuration in inittab or the alternative fbgetty package.
Is this still happening. I have not seen this myself, and am unsure how to reproduce it. Is this an exception from your /etc/inittab file: > # getty never runs under this default setting > 1:2345:respawn:/sbin/getty 38400 tty1 > 2:23:respawn:/sbin/getty 38400 tty2 > 3:23:respawn:/sbin/getty 38400 tty3 > 4:23:respawn:/sbin/getty 38400 tty4 > 5:23:respawn:/sbin/getty 38400 tty5 > 6:23:respawn:/sbin/getty 38400 tty6 > # fbgetty never runs under this alternate setting > 1:2345:respawn:/sbin/fbgetty --issue=/etc/issue.fg /dev/tty1 /dev/fb0 > 2:23:respawn:/sbin/fbgetty --issue=/etc/issue.fg /dev/tty2 /dev/fb0 > 3:23:respawn:/sbin/fbgetty --issue=/etc/issue.fg /dev/tty3 /dev/fb0 > 4:23:respawn:/sbin/fbgetty --issue=/etc/issue.fg /dev/tty4 /dev/fb0 > 5:23:respawn:/sbin/fbgetty --issue=/etc/issue.fg /dev/tty5 > 6:23:respawn:/sbin/fbgetty --issue=/etc/issue.fg /dev/tty6 If so, I suspect init will be confused as the service names (1-6) are used several times. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]