mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>, "Greg KH" <greg@kroah.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: Mon, 10 Jul 2006 09:03:49 -0400	[thread overview]
Message-ID: <9e4733910607100603r5ae1a21ex1a2fa0f045424fd1@mail.gmail.com> (raw)
In-Reply-To: <1152537049.27368.119.camel@localhost.localdomain>

On 7/10/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Llu, 2006-07-10 am 08:41 -0400, ysgrifennodd Jon Smirl:
> > The whole naming scheme encoded into the tty code is incompatible with
> > udev. Udev allows renames and this code isn't aware of them.
>
> The idea is not to break stuff.

I agree with this. I made a mistake with the pts vs pty, why not just
help me fix the mistake instead of rejecting everything? Some the of
the info being reported in /proc/tty/drivers is wrong (vc./0 - from
the devfs attempt?). or missing.

> > 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.
>
> A very large number of users don't bother with udev. Relying on udev is
> not a wise thing to assume, especially in the embedded space.

I'm not going to solve this problem but it is something that needs to
be discussed. Are we really going to maintain parallel naming schemes,
one in-kernel and one out of kernel? I'm not even sure if USB will
work without udev anymore.

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2006-07-10 13:03 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
2006-07-10 13:10     ` Alan Cox
2006-07-10 13:03       ` Jon Smirl [this message]
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=9e4733910607100603r5ae1a21ex1a2fa0f045424fd1@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®