From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: /dev/pts question
Date: 18 Apr 2001 15:29:01 -0700 [thread overview]
Message-ID: <9bl4fd$amr$1@cesium.transmeta.com> (raw)
In-Reply-To: <01041822354404.00617@ElkOS>
Followup to: <01041822354404.00617@ElkOS>
By author: elko <elko@home.nl>
In newsgroup: linux.dev.kernel
>
> as I understand, /dev/pts was created
> to make an end to the overload in /dev/<devices>
> and let the kernel put the entries in /dev/pts
> when they are used/needed/installed.
>
You understand wrong. /dev/pts was constructed because the semantics
of BSD pty's is broken (there are issues with permissions.)
> but still, when I enable /dev/pts, I have to
> keep the /dev/<devices> for backward compatibility
> with already installed applications that rely on them.
You should fix your applications.
> would it be possible/sane to make like a
> /dev/* (some sort of a /dev/B-compatible) besides
> /dev/pts, where the kernel `translates' the
> /dev/<device> request to /dev/* and then
> `translate' that to the correct /dev/pts entry ??
Absolutely not. BSD and Unix98 ptys have different semantics, and
absolutely, positively, must be kept separate -- or you have a
security hole in your machine.
Fix your old applications.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
prev parent reply other threads:[~2001-04-18 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 20:35 /dev/pts question elko
2001-04-18 22:29 ` H. Peter Anvin [this message]
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='9bl4fd$amr$1@cesium.transmeta.com' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.