From owner-freebsd-current Tue Jan 19 05:22:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05111 for freebsd-current-outgoing; Tue, 19 Jan 1999 05:22:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05106 for ; Tue, 19 Jan 1999 05:22:28 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id OAA17681 for freebsd-current@FreeBSD.ORG; Tue, 19 Jan 1999 14:22:22 +0100 (CET) (envelope-from olli) Date: Tue, 19 Jan 1999 14:22:22 +0100 (CET) From: Oliver Fromme Message-Id: <199901191322.OAA17681@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: New syscons + XFree 3.3.3.1 = problem? Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >but that doesn't happen any- > >more. Instead, it uses the current one (i.e. if I'm on ttyv3 > >and start X, it uses ttyv3). Is this intentional, or is it a > >bug? Oops... I'm very sorry for the confusion... it was all my fault. There were as many gettys configured in in /etc/ttys as MAXCONS in the kernel, so XFree wasn't able to allocate an unused vty, obviously. Disabling one getty solved the problem. Maybe this pitfall could be documented somewhere... But then again, maybe I'm the only one who's too dumb to get it right. :-] Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message