From owner-freebsd-hackers Thu Jan 10 12:26:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id A7B3F37B402 for ; Thu, 10 Jan 2002 12:26:17 -0800 (PST) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id g0AKQH713398 for freebsd-hackers@freebsd.org; Thu, 10 Jan 2002 15:26:17 -0500 (EST) (envelope-from bicknell) Date: Thu, 10 Jan 2002 15:26:17 -0500 From: Leo Bicknell To: freebsd-hackers@freebsd.org Subject: serial console + boot blip Message-ID: <20020110202617.GA13083@ussenterprise.ufp.org> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a few machines configured for serial consoles (my first), and have found an oddity. Basically I did the "-P" boot.config thing, and the 'set console=comconsole' in loader.rc. This works fine. I then run a getty on the 'console' in ttys. When connected to a Cisco terminal server, all works well. I telnet to the port, get the serial console, can log in. Most importantly for the problem below when I log out the terminal server automatically drops the telnet connection. I believe this is due to DTR going down after the shell exits, but I'm not positive so it may be some other control signal. Anyway, to the problem. This creates two issues, one I can live with, one I want to fix. 1) If the machine is off, you can't open a telnet connection (no DTR high, I believe). So, when someone first turns it on you have to log in quickly, and miss the first few lines of boot. I can live with this. 2) Once you get in while it's booting, you can watch the boot message. However, when the kernel messages are done and the scripts start (eg, the change from bold to regular on a normal CRT) the connection is closed. It looks like init starting resets the serial port in a way that makes it die again. This is what I would like to fix. As as aside, I'm also thinking it might be useful to have a prompt at that point (on serial console anyway) asking if you want to go into single user mode, since you don't get to select that earlier with a serial console. Have others noticed this behavior? Does anyone know a way to work around it? Does some init genuis know why this happens? -- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message