From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Opinions on removing /proc/tty?
Date: Fri, 7 Jul 2006 22:30:43 -0700 [thread overview]
Message-ID: <20060707223043.31488bca.rdunlap@xenotime.net> (raw)
In-Reply-To: <9e4733910607071956q284a2173rfcdb2cfe4efb62b4@mail.gmail.com>
On Fri, 7 Jul 2006 22:56:51 -0400 Jon Smirl wrote:
> Does anyone use the info in /proc/tty? The hard coded device names
> aren't compatible with udev's ability to rename things.
>
> There also doesn't appear to be any useful info in the drivers portion
> that isn't already available in sysfs. I can add some code to make a
> list of registered line disciplines appear in sysfs.
>
> Does anyone have a problem with deleting /proc/tty if ldisc enum
> support is added to sysfs?
>
> [root@jonsmirl tty]# cat drivers
> /dev/tty /dev/tty 5 0 system:/dev/tty
> /dev/console /dev/console 5 1 system:console
> /dev/ptmx /dev/ptmx 5 2 system
> /dev/vc/0 /dev/vc/0 4 0 system:vtmaster
> serial /dev/ttyS 4 64-67 serial
> pty_slave /dev/pts 136 0-1048575 pty:slave
> pty_master /dev/ptm 128 0-1048575 pty:master
> unknown /dev/tty 4 1-63 console
> [root@jonsmirl tty]#
>
> [root@jonsmirl tty]# cat ldiscs
> n_tty 0
Hi,
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.
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?
Thanks,
---
~Randy
next prev parent reply other threads:[~2006-07-08 5:27 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 [this message]
[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
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=20060707223043.31488bca.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®