From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>, "Greg KH" <greg@kroah.com>
Cc: lkml <linux-kernel@vger.kernel.org>, "Andrew Morton" <akpm@osdl.org>
Subject: Re: [PATCH] Clean up old names in tty code to current names
Date: Mon, 10 Jul 2006 08:41:50 -0400 [thread overview]
Message-ID: <9e4733910607100541i744dd744n16c35c50dae1e98d@mail.gmail.com> (raw)
In-Reply-To: <1152524657.27368.108.camel@localhost.localdomain>
On 7/10/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Llu, 2006-07-10 am 00:11 -0400, ysgrifennodd Jon Smirl:
> > Fix various places in the tty code to make it match the current naming system.
> > pty_slave_driver->driver_name = "pty_slave";
>
>
> NAK to just about all of this. Its gratuitous breaking of existing apps,
> it achieves nothing and some of it like the pty stuff is just plain
> incorrect anyway.
The whole naming scheme encoded into the tty code is incompatible with
udev. Udev allows renames and this code isn't aware of them.
I thought the idea behind udev was to remove all of this naming code
from the kernel and handle it in user space. So if I want legacy
device names I would add a section to /etc/udev to create them. Udev
is already capable of doing this.
> If you want to add sysfs interfaces to the tty code great, but please
> leave the existing, relied up, functional and effectively user space ABI
> tty files alone.
So far I haven't identified anything that is really needed that isn't
already available in sysfs.
It does seem that we are missing a user space library call for
converting a device number into a device name using the udev database.
On 7/9/06, Albert Cahalan <acahalan@gmail.com> wrote:
> BSD just uses devname(3) in libc, which asks the kernel via
> the kern.devname sysctl. So, /proc/sys/kern/devname for us.
> This is essentially what /proc/tty/drivers is today, except
> that FreeBSD standardized on a fully functional devfs.
>
> Solaris uses _ttyname_dev(dev_t,buf,bufsize), also in libc.
> This is horribly slow, involving a recursive search of
> directories listed in the /etc/ttysrch file. The interface
> is nice though. You get: ttyname, ttyname_r, _ttyname_dev.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2006-07-10 12:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 4:11 Jon Smirl
2006-07-10 4:54 ` Andrew Morton
2006-07-10 7:14 ` H. Peter Anvin
2006-07-10 9:44 ` Alan Cox
2006-07-10 12:41 ` Jon Smirl [this message]
2006-07-10 13:10 ` Alan Cox
2006-07-10 13:03 ` Jon Smirl
2006-07-10 13:12 ` CaT
2006-07-10 13:18 ` Jon Smirl
2006-07-10 13:43 ` Alan Cox
2006-07-10 14:07 ` Jon Smirl
2006-07-10 14:17 ` Jan Engelhardt
2006-07-10 14:37 ` Alan Cox
2006-07-10 14:42 ` Antonino A. Daplas
2006-07-10 14:57 ` Jon Smirl
2006-07-10 15:19 ` Alan Cox
2006-07-10 15:10 ` Valdis.Kletnieks
2006-07-10 15:21 ` Russell King
2006-07-10 15:38 ` Valdis.Kletnieks
2006-07-10 15:35 ` Antonino A. Daplas
2006-07-10 15:54 ` Jon Smirl
2006-07-10 16:04 ` H. Peter Anvin
2006-07-10 22:14 ` Jan Engelhardt
2006-07-10 18:13 ` Alistair John Strachan
2006-07-11 21:54 ` Greg KH
2006-07-11 21:52 ` Greg KH
2006-07-11 2:18 Albert Cahalan
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=9e4733910607100541i744dd744n16c35c50dae1e98d@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=hpa@zytor.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®