mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"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 11:54:47 -0400	[thread overview]
Message-ID: <9e4733910607100854x250e9d3aga027ef5e156ec34e@mail.gmail.com> (raw)
In-Reply-To: <44B273B9.8050308@gmail.com>

On 7/10/06, Antonino A. Daplas <adaplas@gmail.com> wrote:
> Alan Cox wrote:
> > Ar Llu, 2006-07-10 am 10:57 -0400, ysgrifennodd Jon Smirl:
> >>> A few apps do rely on /proc/tty/drivers for the major-minor
> >>> to device name mapping. /dev/vc/0 does not exist (unless
> >>> created manually) without devfs.
> >> This is why I questioned if /proc/tty was really in use, it contains
> >> an entry that is obviously wrong for my system.
> >
> > Which tools already know about.
>
> True.  I see this code snippet many times:

BSD has /dev/vc/0 right? I suspect that code is there to support BSD
and make the app portable.

As far as I know the only time Linux has ever had /dev/vc/0 was during
the brief excursion into devfs land. At that time /proc/tty/drivers
was modified to support devfs.  But now devfs has been removed and the
device has reverted back to tty0. But /proc/tty/drivers wasn't
adjusted for devfs removal.

> fd = open("/dev/vc/0", FLAGS);
> if (fd == -1)
>         fd = open("/dev/tty0", FLAGS);
>
> > What is so hard to understand about the
> > idea that pointless random changes break stuff and don't fix things.
>
> But since we're killing devfs, changing /dev/vc/0 to /dev/tty0 will be one
> of the nails in devfs' coffin :-)
>
> Tony
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2006-07-10 15:55 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
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 [this message]
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=9e4733910607100854x250e9d3aga027ef5e156ec34e@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@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®