From: Greg KH <greg@kroah.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
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: Tue, 11 Jul 2006 14:52:37 -0700 [thread overview]
Message-ID: <20060711215237.GA663@kroah.com> (raw)
In-Reply-To: <9e4733910607100541i744dd744n16c35c50dae1e98d@mail.gmail.com>
On Mon, Jul 10, 2006 at 08:41:50AM -0400, Jon Smirl wrote:
> 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.
No, it's not incompatible at all.
Sure udev lets you rename things stupidly, but you can do the same thing
with a simple 'rm' and 'mknod' too.
A good udev setup will follow the LSB naming scheme, and also provide a
persistent device naming scheme for some classes of devices. If your
distro does not do this, then file bugs and complain to them.
In short, this is not a kernel problem.
> I thought the idea behind udev was to remove all of this naming code
> from the kernel and handle it in user space.
No, that was never the idea behind udev. udev was created to allow
persistent device naming to be possible, that's all. It was not
intended to rip all naming out of the kernel, only the non-LSB compliant
names.
Although some people at times have proposed that the in-kernel names be
removed entirely, saner minds have always prevailed.
> 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.
udev should already do this. If not, then blame your distro for setting
it up improperly.
> >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.
Again, if you really want this, add the option to udevinfo. Don't keep
complaining about it...
And no, I would never expect the ps tools to rely on the udev package,
that would be insane.
thanks,
greg k-h
next prev parent reply other threads:[~2006-07-11 21:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 4:11 [PATCH] Clean up old names in tty code to current names 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20060711215237.GA663@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.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