From: Randy Dunlap <randy.dunlap@oracle.com>
To: Bill Nottingham <notting@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC, BAD IDEA] /proc/tty/console
Date: Wed, 27 Feb 2008 10:56:09 -0800 [thread overview]
Message-ID: <20080227105609.bf26c592.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080227185225.GB3137@nostromo.devel.redhat.com>
On Wed, 27 Feb 2008 13:52:25 -0500 Bill Nottingham wrote:
> Randy Dunlap (randy.dunlap@oracle.com) said:
> > > I'm not seriously proposing this. But, as far as I can tell, this
> > > information isn't exposed to userspace anywhere, and it's a useful
> > > thing to know. I'm certainly open for better ideas on how to expose
> > > this (sysfs attributes? other?)
> > >
> > > ....
> > >
> > > 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
> > >
> >
> > So it omits other consoles (non-tty) intentionally?
> > or does it include them even though the procfs filename contains "tty"?
>
> It only does consoles that have a tty_driver, as those are the ones I'd
> find most interesting.
>
> > Anyway, I'd like to see something like this.
> > Compare http://www.xenotime.net/linux/patches/consoles-list.patch
> > (April-2006).
>
> Reading that, unless I'm missing something, you'd lose the device name
> distinction (i.e., *which* serial port).
I don't recall about that, but it would be Bad if correct.
I meant to list *all* consoles. I'm interested in netconsole,
console=lp0, console=ttyUSB0, etc., as well as serial port consoles.
Thanks.
---
~Randy
next prev parent reply other threads:[~2008-02-27 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 18:18 Bill Nottingham
2008-02-27 18:37 ` Randy Dunlap
2008-02-27 18:52 ` Bill Nottingham
2008-02-27 18:56 ` Randy Dunlap [this message]
2008-02-29 6:49 ` Andrew Morton
2008-02-29 15:07 ` Bill Nottingham
2008-02-29 20:49 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080227105609.bf26c592.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®