From owner-freebsd-current Mon Apr 10 09:35:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA07285 for current-outgoing; Mon, 10 Apr 1995 09:35:58 -0700 Received: from tcsi.tcs.com (tcsi.tcs.com [137.134.41.11]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA07278 for ; Mon, 10 Apr 1995 09:35:56 -0700 Received: from tcs.com by tcs.com (8.6.10/8.6.6) with ESMTP id JAA08534 for ; Mon, 10 Apr 1995 09:35:24 -0700 Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.6.10/8.6.10) with ESMTP id JAA29787 for ; Mon, 10 Apr 1995 09:35:23 -0700 From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id JAA00591 for current@FreeBSD.org; Mon, 10 Apr 1995 09:35:21 -0700 Message-Id: <199504101635.JAA00591@cozumel.tcs.com> Subject: Problem with libutil (login_tty) To: current@FreeBSD.org Date: Mon, 10 Apr 1995 09:35:20 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1314 Sender: current-owner@FreeBSD.org Precedence: bulk "/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.