Date: Fri, 29 Feb 2008 12:49:42 -0800
From: Andrew Morton <akpm@linux-foundation.org>
To: Bill Nottingham <notting@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC, BAD IDEA] /proc/tty/console
Message-Id: <20080229124942.fd402273.akpm@linux-foundation.org>
In-Reply-To: <20080229150730.GA8209@nostromo.devel.redhat.com>
References: <20080227181857.GA3137@nostromo.devel.redhat.com>
	<20080228224923.fbbd97dc.akpm@linux-foundation.org>
	<20080229150730.GA8209@nostromo.devel.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1321
Lines: 34

On Fri, 29 Feb 2008 10:07:30 -0500
Bill Nottingham <notting@redhat.com> wrote:

> Andrew Morton (akpm@linux-foundation.org) said: 
> > > The attached patch adds /proc/tty/console. The contents of it are
> > > simply a description of the current drivers attached to /dev/console.
> > > For example, a boot with 'console=ttyS3,115200n1 console=tty0' would
> > > yield:
> > > 
> > > # cat /proc/tty/console
> > > unknown             /dev/tty0
> > > serial              /dev/ttyS3
> > 
> > I must say that the what-consoles-are-registered problem makes my head spin
> > sometimes too.  Seems a worthy objective.
> > 
> > However I think that a bunch of plain old printks which are emitted when a
> > console is added or removed would suffice?
> 
> We already do that in register_console(), albeit without flags.

oh.

> My concern is I'd like to easily programmatically do something with this
> info - ideally it would be in sysfs so it can easily be used from udev
> or something similar.

That's the sort of information which really must be in the changelog, fully
spelled out.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/