From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
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 19:13:45 +0100 [thread overview]
Message-ID: <200607101913.45070.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <44B26752.9000507@gmail.com>
On Monday 10 July 2006 15:42, Antonino A. Daplas wrote:
> Jon Smirl wrote:
> > On 7/10/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >> Ar Llu, 2006-07-10 am 09:03 -0400, ysgrifennodd Jon Smirl:
> >> > 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.
> >>
> >> What are you trying to achieve and where are you trying to get. If you
> >> want better info for the tty layer then get the new info working in
> >> sysfs first. Then when people are generally using sysfs you can worry
> >> about cleaning up/removing/breaking the old stuff.
> >
> > Before the change /proc/tty/drivers shows this:
> >
> > [jonsmirl@jonsmirl ~]$ cat /proc/tty/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
>
> vtmaster was /dev/tty0 in 2.2.x, changed to /dev/vc/0 probably
> because of devfs. I would tend to agree with the change of at least
> this part.
>
> 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.
Create a file in /etc/udev/rules.d. Add to it the following.
# devfs-ify vt devices
KERNEL="tty[0-9]*", NAME="vc/%n"
Now John's names are broken.
As Alan's wisely pointed out, it's utterly insane to try to "fix" a legacy
file when it a) can never match all possible, legal, current configurations
and b) shouldn't be used for anything important anyway.
It'd be better to CONFIG out this directory and see what breaks. Then we can
decide if we should (or provide distributors the option to) remove it.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-07-10 18:13 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
2006-07-10 16:04 ` H. Peter Anvin
2006-07-10 22:14 ` Jan Engelhardt
2006-07-10 18:13 ` Alistair John Strachan [this message]
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=200607101913.45070.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®