From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: adaplas@gmail.com, greg@kroah.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: Opinions on removing /proc/tty?
Date: Sun, 9 Jul 2006 10:35:29 -0700 [thread overview]
Message-ID: <20060709103529.bf8a46a4.rdunlap@xenotime.net> (raw)
In-Reply-To: <9e4733910607090645l236f17f1sb9778f0fc6c6ca01@mail.gmail.com>
On Sun, 9 Jul 2006 09:45:06 -0400 Jon Smirl wrote:
> On 7/9/06, Antonino A. Daplas <adaplas@gmail.com> wrote:
> > Jon Smirl wrote:
> > > On 7/9/06, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> > >> On Sat, 8 Jul 2006 01:56:02 -0400 Jon Smirl wrote:
> > >>
> > >> > On 7/8/06, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> > >> > > I don't know how well this is an answer to your question,
> > >> > > but I would like to be able to find a list of registered "consoles,"
> > >> > > whether they be serial, usbserial, netconsole, lp, or whatever.
> > >> > > /proc/tty/drivers does that partially.
> > >> >
> > >> > Console is an overloaded word. Do you want to know where it is legal
> > >> > to send system log output to, or do you want to know where you can log
> > >> > in from? There was a thread earlier that talked a little about
> > >> > controlling this.
> > >>
> > >> I have a working definition:
> > >> I want to see a list of drivers that have called register_console().
> > >>
> > >> > > I have a patch that also does it in /proc/consoles:
> > >> > > http://www.xenotime.net/linux/patches/consoles-list.patch
> > >> > > Is somewhere in /sys the right place to find a list of all consoles?
> > >> >
> > >> > /sys is the right place for this info but a class does not exist for
> > >> it yet.
> > >>
> > >> I want a list of registered consoles. How would I express that in /sys ?
> > >
> > > You could make the list appear as an attribute in
> > > /sys/class/tty/console. You will need to all a little sysfs code after
> > > the console tty device is created.
> > >
> >
> > That would violate the one file, one value rule and GregKH will drop
> > it like a hot potato.
> >
> > A better solution is to have /sys/class/console.
>
> The one value rule is for things that can be changed. For, example, I
> see no problem with using the graphics/modes attribute to see a list
> of legal modes, and then using graphics/mode to set or view the
> currently active mode. Why can't we have a read-only attribute that
> displays the list of available consoles?
We should be able to do that somewhere/somehow, but /sys does
not allow for it in one file, like Tony said.
---
~Randy
next prev parent reply other threads:[~2006-07-09 17:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 2:56 Jon Smirl
2006-07-08 5:30 ` Randy.Dunlap
[not found] ` <9e4733910607072256q65188526uc5cb706ec3ecbaee@mail.gmail.com>
2006-07-09 5:04 ` Randy.Dunlap
[not found] ` <9e4733910607082220v754a000ak7e75ae4042a5e595@mail.gmail.com>
2006-07-09 5:27 ` Randy.Dunlap
2006-07-09 10:07 ` Antonino A. Daplas
[not found] ` <9e4733910607090645l236f17f1sb9778f0fc6c6ca01@mail.gmail.com>
2006-07-09 17:35 ` Randy.Dunlap [this message]
2006-07-09 23:31 ` Antonino A. Daplas
[not found] ` <9e4733910607091744k273a7351l16abbcc6ff8c4bbd@mail.gmail.com>
2006-07-11 22:01 ` Greg KH
[not found] ` <9e4733910607111532s3fc2bb52q3f0247a9f2289d4e@mail.gmail.com>
2006-07-13 18:37 ` Greg KH
2006-07-08 7:40 ` Mike Galbraith
2006-07-08 14:12 ` Jon Smirl
2006-07-08 14:48 ` Alan Cox
2006-07-08 16:20 ` Jon Smirl
2006-07-08 17:20 ` Russell King
2006-07-11 22:03 ` Greg KH
2006-07-08 16:12 ` Greg KH
2006-07-09 5:30 Albert Cahalan
2006-07-09 14:04 ` Jon Smirl
2006-07-09 16:23 ` Albert Cahalan
2006-07-09 17:00 ` Ray Lee
2006-07-09 17:08 ` Ray Lee
2006-07-09 19:26 ` Albert Cahalan
2006-07-09 19:31 ` Russell King
2006-07-09 19:57 ` Albert Cahalan
2006-07-10 14:02 ` Jan Engelhardt
2006-07-10 15:06 ` Albert Cahalan
2006-07-10 22:17 ` Jan Engelhardt
2006-07-11 1:07 ` Albert Cahalan
2006-07-11 1:48 ` H. Peter Anvin
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=20060709103529.bf8a46a4.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=adaplas@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome