linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does anyone still care about BSD ptys?
Date: Mon, 9 Feb 2004 19:06:51 +0100	[thread overview]
Message-ID: <20040209180651.GA15842@suse.de> (raw)
In-Reply-To: <c07i5r$ctq$1@news.cistron.nl>

 On Mon, Feb 09, Miquel van Smoorenburg wrote:

> In article <c07c67$vrs$1@terminus.zytor.com>,
> H. Peter Anvin <hpa@zytor.com> wrote:
> >Does anyone still care about old-style BSD ptys, i.e. /dev/pty*?  I'm
> >thinking of restructuring the pty system slightly to make it more
> >dynamic and to make use of the new larger dev_t, and I'd like to get
> >rid of the BSD ptys as part of the same patch.
> 
> bootlogd(8) which is used by Debian and Suse is started as the
> first thing at boottime. It needs a pty, and tries to use /dev/pts
> if it's there but falls back to BSD style pty's if /dev/pts isn't
> mounted - which will be the case 99% of the time.

mounting proc and dev/pts is the first thing our boot script does, since
a very long time. So it will not break anything.

-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG

  parent reply	other threads:[~2004-02-09 18:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09  7:17 Does anyone still care about BSD ptys? H. Peter Anvin
2004-02-09  7:21 ` David Weinehall
2004-02-09  7:29   ` H. Peter Anvin
2004-02-09  8:12     ` Ricky Beam
2004-02-09  8:19       ` H. Peter Anvin
2004-02-09  8:59 ` Miquel van Smoorenburg
2004-02-09 10:09   ` viro
2004-02-09 10:47     ` Miquel van Smoorenburg
2004-02-10  1:33     ` bill davidsen
2004-02-10  2:07       ` H. Peter Anvin
2004-02-09 18:06   ` Olaf Hering [this message]
2004-02-09  9:29 ` Nick Craig-Wood
2004-02-09 12:47   ` Jamie Lokier
2004-02-09 13:40     ` Nick Craig-Wood
2004-02-09 14:00       ` Richard B. Johnson
2004-02-09 17:51         ` Dominik Kubla
2004-02-09 18:27           ` Richard B. Johnson
2004-02-09 20:59             ` Athanasius
2004-02-10 11:16             ` Dominik Kubla
2004-02-10 17:19               ` H. Peter Anvin
2004-02-10  0:47 ` Karl Tatgenhorst
2004-02-10  0:52   ` H. Peter Anvin
2004-02-10  1:35     ` Karl Tatgenhorst
  -- strict thread matches above, loose matches on Subject: below --
2004-02-09 13:49 Albert Cahalan
2004-02-09 17:14 ` H. Peter Anvin
2004-02-09 17:18   ` Albert Cahalan
2004-02-09 20:32     ` Andries Brouwer
2004-02-10 11:40     ` Dominik Kubla
     [not found] <c07c67$vrs$1@terminus.zytor.com.suse.lists.linux.kernel>
     [not found] ` <c07i5r$ctq$1@news.cistron.nl.suse.lists.linux.kernel>
     [not found]   ` <20040209100940.GF21151@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
     [not found]     ` <20040209104729.GA19401@traveler.cistron.net.suse.lists.linux.kernel>
2004-02-09 14:45       ` Andi Kleen
2004-02-09 17:23         ` H. Peter Anvin
2004-02-09 16:57 Joerg Pommnitz
2004-02-10 17:23 ` H. Peter Anvin
     [not found] <1ne1M-1Oc-1@gated-at.bofh.it>
2004-02-10 19:47 ` Bill Davidsen
2004-02-10 19:51 ` Bill Davidsen
2004-02-10 21:52   ` Theodore Ts'o
2004-02-10 22:02     ` H. Peter Anvin
2004-02-11  5:31       ` Theodore Ts'o

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=20040209180651.GA15842@suse.de \
    --to=olh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    /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;
as well as URLs for NNTP newsgroup(s).