From owner-freebsd-stable@FreeBSD.ORG Sat May 8 13:54:42 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3F5D16A4CE for ; Sat, 8 May 2004 13:54:42 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F316243D2F for ; Sat, 8 May 2004 13:54:41 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i48KsOiY046173; Sat, 8 May 2004 16:54:25 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i48KsOfp046170; Sat, 8 May 2004 16:54:24 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 8 May 2004 16:54:24 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Rob In-Reply-To: <409B40EC.3080900@users.sourceforge.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: Bruce Hunter Subject: Re: Connecting to a Headless machine, after install X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 May 2004 20:54:42 -0000 On Fri, 7 May 2004, Rob wrote: > Bruce Hunter wrote: > > I have setup a headless machine via a null modem cable. Instalation went > > fine. The only problem now, is connecting to the machine after the > > install. When I #cu -l /dev/cuaao/ > > I see the boot process, but it gets to the date prompt but doesn't show > > the login: > > i did install ssh, but won't let me login with the password I set for > > root. Any other methods for connecting? This system is connected in my > > local network, with a firewall protecting my systems. > > - i am not running xserver on this system ... > Funny, that I'm struggling with opposite problem: I do not get the > boot messages over the serial cable, but do get the login prompt, > which I do not understand :(. > > For the login prompt, I have following in /etc/ttys on the headless PC: > > ttyd0 "/usr/libexec/getty std.9600" unknown on secure > > but be sure the serial port is enabled in the BIOS, and you have > serial port support compiled into your kernel. > Your cu command should then work, I suppose. You both have half of the solution, apparently, just different halves :-). To configure my boxes for serial console operation, I do two things: (1) Enable the ttyd0 entry in /etc/ttys by changing "off" to "on" (2) Add the following line to /boot/loader.conf: console="comconsole" This one can be done in a couple of ways, including flags in boot.config for the first stage loader. The first action above tells init to launch getty+login on the serial port. The second action above tells the kernel to direct /dev/console and low level console output to the serial port. Note that nothing prohibits you from leaving ttyv0 turned on when running with a serial console so you could still log in on the VGA/keyboard console if you wanted to. There are also some options in conscontrol(8) to send output to multiple console devices, but there are some limitations to multiple console operation. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research