From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: console questions Date: Tue, 07 Aug 2007 08:59:42 +0100 Message-ID: References: <20070806212923.GA22302@fc.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070806212923.GA22302@fc.hp.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Aron Griffis , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 6/8/07 22:29, "Aron Griffis" wrote: > 1. xencons=xvc works and makes more sense than clobbering ttyS0 by > default. Is there some reason that the default for xencons is > still ttyS on dom0? Sure hvc is coming, but would it be reasonable > to change the default for xencons in the meantime? Now done for dom0 and domU. Users will need to change their inittab to getty xvc0, or need to place 'xencons=tty' on their kernel command line. > 2. xencons=xvc1 and upward is accepted by the kernel, but it just > changes the userland naming. The major/minor remains the same at > 204/191. What's the point of this? Is there any reason to allow > anything other than xencons=xvc or xencons=xvc0? What's the better alternative? Needlessly penalise a typo? -- Keir