From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-mm5 devpts filesystem doesn't work
Date: Wed, 14 Apr 2004 14:38:30 +0200 [thread overview]
Message-ID: <407D30C6.3040009@aitel.hist.no> (raw)
In-Reply-To: <20040413011133.2d15a4d6.akpm@osdl.org>
Andrew Morton wrote:
> Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
>>I tried stepping up from 2.6.5-rc3-mm4 to 2.6.5-mm4.
>>This Quokka seems too zonked to work though.
>>
>>It came up, but I couldn't run "xterm". Trying from
>>the xemacs shell I saw an error message about not enough ptys.
>>I use the devpts fs mounted on /dev/pts
>>
>>It mounts just fine, but doesn't work apparently. There are no
>>such problems with 2.6.5-rc3-mm4
>
>
> Is this 2.6.5-mm4 or 2.6.5-mm5?
>
> If the latter, try reverting pty-allocation-first-fit.patch
Oops, it was 2.6.5-mm5, sorry. I'm compiling
2.6.5-mm5-1 now
Helge Hafting
next prev parent reply other threads:[~2004-04-14 12:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 5:17 2.6.5-mm5 Andrew Morton
2004-04-13 7:38 ` 2.6.5-mm5 Kurt Fitzner
2004-04-13 7:56 ` 2.6.5-mm5 Nick Piggin
2004-04-13 8:07 ` 2.6.5-mm5 devpts filesystem doesn't work Helge Hafting
2004-04-13 8:11 ` Andrew Morton
2004-04-13 8:36 ` Sean Neakums
2004-04-13 8:39 ` Andrew Morton
2004-04-13 9:19 ` Marc-Christian Petersen
2004-04-13 9:26 ` Andrew Morton
2004-04-14 12:38 ` Helge Hafting [this message]
2004-04-13 11:36 ` 2.6.5-mm5: no help text for S2IO_NAPI Adrian Bunk
2004-04-13 16:02 ` 2.6.5-mm5 (compile stats) John Cherry
2004-04-15 15:30 ` 2.6.5-mm5 markw
2004-04-15 19:42 ` 2.6.5-mm5 Andrew Morton
2004-04-16 14:51 ` 2.6.5-mm5 markw
2004-04-16 22:59 ` 2.6.5-mm5 Nick Piggin
2004-04-16 23:03 ` 2.6.5-mm5 markw
2004-04-18 9:20 ` 2.6.5-mm5 Nick Piggin
2004-04-19 14:53 ` 2.6.5-mm5 markw
2004-04-19 14:51 ` 2.6.5-mm5 markw
2004-04-16 1:57 ` 2.6.5-mm5 Nick Piggin
2004-04-16 10:34 ` 2.6.5-mm5 Ingo Molnar
2004-04-16 14:52 ` 2.6.5-mm5 markw
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=407D30C6.3040009@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=akpm@osdl.org \
--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