All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Opinions on removing /proc/tty?
Date: Sun, 09 Jul 2006 18:07:25 +0800	[thread overview]
Message-ID: <44B0D55D.2010400@gmail.com> (raw)
In-Reply-To: <9e4733910607082220v754a000ak7e75ae4042a5e595@mail.gmail.com>

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.

Tony

  parent reply	other threads:[~2006-07-09 10:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08  2:56 Opinions on removing /proc/tty? 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 [this message]
     [not found]           ` <9e4733910607090645l236f17f1sb9778f0fc6c6ca01@mail.gmail.com>
2006-07-09 17:35             ` Randy.Dunlap
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
  -- strict thread matches above, loose matches on Subject: below --
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=44B0D55D.2010400@gmail.com \
    --to=adaplas@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.