-- Hi Erik, Quick response with answer to your question:
Mats Erik Andersson <[email protected]> [2013-09-20 01:53:48 +0200]: > > In case you have tried inetutils-telnetd in Arch Linux, can you connect > from another system without observing any disruptions? > Below is what I see. Behavior seems normal to me. One caveat: The "could not get file descriptor for console" error is something I see using all remote login methods (e.g. slogin) as well. This has been the case for quite a while. I think it may have something to do with improper default setup of systemd vconsole.conf, but since it has never caused me any observable trouble, I have always ignored it. HTH. Regards, Glenn ========================= begin inline attachment ================== XXX> telnet XXX Trying 192.168.1.18... Connected to XXX Escape character is '^]'. Linux 3.11.1-1-ARCH (XX.XXXXXX.XXX) (pts/0) huh login: XXX Password: Last login: Fri Sep 20 09:40:53 on tty2 Couldn't get a file descriptor referring to the console WARNING: gdg console keyboard not loaded, insanity may occur. XXX$> stty speed 38400 baud; line = 0; erase = ^H; -brkint -imaxbel HUH$> stty -a speed 38400 baud; rows 34; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke ========================= end inline attachment ==================
