Hello, Firstly, the 64bit port of the Hurd is very recent, so expect things not to be completely done.
Borja Tarraso, le dim. 31 mai 2026 18:58:07 +0300, a ecrit: > The default state of /etc/default/hurd-console is ENABLE="false", so > the boot-time path is intentionally off; Yes, because the hurd console was originally just crashing on hurd-amd64. It got fixed in the meanwhile, and AFAICT, the latest preinstalled image does have ENABLE="true3. > # exact command from > # https://www.debian.org/ports/hurd/hurd-install > nohup console -d vga -d pc_mouse --repeat=mouse \ > -d pc_kbd --repeat=kbd \ > -d generic_speaker -c /dev/vcs \ > > /tmp/hurd-console.log 2>&1 & > sleep 4 > jobs -> [1]+ Running console ... > ps -A | grep console -> root 67 ... console -d vga ... > cat /tmp/hurd-console.log -> (empty, console wrote nothing) > > # re-check > showtrans /dev/cons -> exit 1 (still no translator) Note that showtrans only shows the passive translators, not the active translators. Running the console sets an active translator, not a passive. You want to use fsysopts to see the actually active translator. > ls -l /dev/cons -> still -rw------- 1 root root 0 That is surprising, it should be a directory with kbd, mouse entries. Are you really running the latest hurd-amd64 image? > 1. Is there a prerequisite step the install doc omits on this > image, e.g. `cd /dev && ./MAKEDEV vcs tty1 ... tty6` No, that's all pre-done when building the images. > 2. NexusSfan's working setup has /dev/cons/kbd as chrdev 101 > 33751128; the original 0.9 baseline (hurd 1:0.9.git20230520-7) Don't care about major/minor, they are meaningless on micro-kernel systems since you are not actually opening devices from a kernel, but just from the translator that happens to be sitting there. > 3. Independently of the above, would a change of the default > /etc/default/hurd-console ENABLE from "false" to "true" be > welcome? AFAIK it's already there in the latest image. Samuel
