From owner-freebsd-current@FreeBSD.ORG Sun May 24 09:45:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 050AF1065678; Sun, 24 May 2009 09:45:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D46818FC26; Sun, 24 May 2009 09:45:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 5FDAE46B38; Sun, 24 May 2009 05:45:48 -0400 (EDT) Date: Sun, 24 May 2009 10:45:48 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ed Schouten In-Reply-To: <20090524091436.GR1271@hoeg.nl> Message-ID: References: <20090524091436.GR1271@hoeg.nl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-xen@freebsd.org, Adrian Chadd , FreeBSD Current Subject: Re: Default Xen PVM console? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2009 09:45:49 -0000 On Sun, 24 May 2009, Ed Schouten wrote: > * Adrian Chadd wrote: >> * Modify the xenconsole driver to attach to ttyv0 (via a kernel environment >> variable) so /etc/ttys doesn't need modifying (but this may confuse tools >> that assumes /dev/ttyvX == syscons.) > > Please don't. Someone on IRC told me Xen also has some framebuffer feature. > Say, someone would port syscons to Xen, the naming would conflict with the > console device node. /dev/xc0 is good enough. I even think it should have > been called ttyx0, not xc0. Given that there will be increasing levels of support for "pass-through" hardware access in virtual machine environments and a trend in the direction of virtualization-friendly hardware, we shouldn't preclude the possibility of something a lot closer to syscons working inside of Xen in the future. This means we should leave the syscons device names open so that syscons can claim them if desired. Robert N M Watson Computer Laboratory University of Cambridge