Hi all, I was able to set up the hurd console to run on system start-ups/reboots according to http://www.debian.org/ports/hurd/hurd-install. However, along the way, I noticed some issues when trying xbd or pc_kbd as the keyboard option. I don't know if it's a bug, or not, but I figured I'll share my experience:
The two options I considered and changed in /etc/default/hurd-console were: KBD && KBD_REPEAT 1) KBD='-d pc_kbd' && KBD_REPEAT='-repeat=kbd' - worked fine; upon reboot the hurd console started up automatically 2) KBD='-d xkb' && KBD_REPEAT='-repeat=xkb' - the hurd console did not start, and the last kernel boot message I got before the mach console login line was "task 2009678 deallocation an invalid port 6, most probably a bug." 3) KBD='-d xkb' && KBD_REPEAT='-repeat=kbd' - the hurd console did not start, and the last kernel boot message I got before the mach console login line was "task 2009678 deallocation an invalid port 6, most probably a bug." 4) KBD='-d xkb' && no KBD_REPEAT (line commented out) - the hurd console did not start, and the last kernel boot message I got before the mach console login line was "task 2009670 deallocation an invalid port 6, most probably a bug." 5) KBD='-d pc_kbd' && KBD_REPEAT='-repeat=xkb' - worked fine; upon reboot the hurd console started up automatically So it seems like the hurd console starts on reboot only when KBD='-d pc_kbd', regardless of the KBD_REPEAT option. God bless David Hiran Watson e: [email protected]
