Thanks for providing that! I started it up in a qemu-kvm VM, and this is the first time in years I've actually had any kind of running Hurd. (It's pathetic for me, I know.) It hung for a dubiously long time at "Starting MTA:" and took nearly another minute to barf about something after I hit ^C there. But it made it to the login shell, so nicely done! (Not that you can really now expect me to actually go and doing anything for Hurd after all these years...sorry.)
I do see a lot of "kd_setleds1: unexpected state (1)" when using the VM console keyboard. w shows 6 login instances on virtual consoles with an entertaining variety of inexplicable idle times, which correspond to the atime values of the /dev/tty[1-6] (underyling?) nodes (I guess I just explained them, so I lied about them being inexplicable). The entire existence of the console server is so new to me that I have no idea which keystrokes switch the virtual consoles or if I'm even near being connected to that whole reality after logging in on /dev/console (hmm, I guess I'm not). Is there a working dhcp client these days, or do I have to figure out which IP address on the virtual subnet virt-manager assigned me and just settrans -p /servers/socket/2 by hand? Thanks, Roland
