From owner-freebsd-hackers Sun Nov 26 19:53:52 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA25086 for hackers-outgoing; Sun, 26 Nov 1995 19:53:52 -0800 Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA25081 for ; Sun, 26 Nov 1995 19:53:48 -0800 Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.6.12/8.6.12) with ESMTP id VAA02826; Sun, 26 Nov 1995 21:53:45 -0600 Received: from localhost by solaria.sol.net (8.5/8.5) id VAA21150; Sun, 26 Nov 1995 21:54:40 -0600 From: Joe Greco Message-Id: <199511270354.VAA21150@solaria.sol.net> Subject: Re: Argh, lost console :-( To: maral@webnet.com.au (Peter Marelas) Date: Sun, 26 Nov 95 21:54:38 CST Cc: hackers@freebsd.org In-Reply-To: from "Peter Marelas" at Nov 25, 95 05:06:10 am X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Content-Length: 721 Sender: owner-hackers@freebsd.org Precedence: bulk > The README in XF86312 says to start xdm from a tty in /etc/ttys > > The easiest way to automatically start the display manager on boot is > to add a line in /etc/ttys to start it on one of the unoccupied > virtual terminals: Yeah, yeah, we know :-) and that might be a cure for the symptom. However, it would be nice to have a cure for the problem.... I have seen consoles get into interesting states every once in a while, and it is really NOT ideal to have to reboot the machine to clear it up. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847