Date: Mon, 10 Apr 1995 09:35:20 -0700 (PDT) From: Douglas Ambrisko <ambrisko@tcs.com> To: current@FreeBSD.org Subject: Problem with libutil (login_tty) Message-ID: <199504101635.JAA00591@cozumel.tcs.com>
index | next in thread | raw e-mail
"/usr/libexec/getty" is busted in the latest snap. When given the device to run getty on (ie. "/usr/libexec/getty std.9600 ttyd0") it fails in login_tty() (which is ignored since the error state is not checked when it returns). In login_tty.c, the login_tty() call fails on the ioctl and return immediately and therefore does not setup stdio to the specified file-descriptor. A quick hack was to ignore the status of the ioctl so that that stdio was switched to the new file-descriptor and now it works a wee bit better. Atleast now I get a getty on my serial console to talk to me when I logout and log back in! Before, my serial system would only work with the first login after a reboot. When I would logout, I wouldn't get the getty login banner again. Note this is not a fix, since I haven't persued the ioctl problem, so this is mostly a heads up. The serial console stuff works great, one thing I haven't tried yet is to do an install via the serial console. Also I ran into a problem of tip'ing into my serial machine from another FreeBSD machine, in that I didn't have my "/etc/remote" config setup for 8 bit, no parity. Having 7 bit, even parity would let me login to the serial machine but would mess up the shell. Some documentation on this my be helpfull (maybe I just missed it). Doug A.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504101635.JAA00591>