From: Nick Orlov <bugfixer@list.ru>
To: Christoph Hellwig <hch@infradead.org>,
Andrei Ivanov <andrei.ivanov@ines.ro>,
Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.67-mm4
Date: Fri, 18 Apr 2003 18:10:29 -0400 [thread overview]
Message-ID: <20030418221029.GA3956@nikolas> (raw)
In-Reply-To: <20030418225447.A8626@infradead.org>
On Fri, Apr 18, 2003 at 10:54:47PM +0100, Christoph Hellwig wrote:
> On Fri, Apr 18, 2003 at 04:54:03PM -0400, Nick Orlov wrote:
> > In my case sshd was not able to allocate pts...
> > Actually it was not possible to allocate pts under 2.5.67-mm4 at all.
>
> do you have the devpts filesystem mounted on /dev/pts/ ?
No, I don't.
I'm using devfs and it works perfectly under 2.5.67-mm3.
Below is part of my .config related to devpts and devfs:
nick@nikolas:/boot$ egrep "DEVFS|DEVPTS" config-2.5.67-mm4-1
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
BTW, system is Debian/unstable, daily updated.
Thanks,
Nick.
--
With best wishes,
Nick Orlov.
next prev parent reply other threads:[~2003-04-18 21:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 19:37 2.5.67-mm4 Andrei Ivanov
2003-04-18 20:54 ` 2.5.67-mm4 Nick Orlov
2003-04-18 21:54 ` 2.5.67-mm4 Christoph Hellwig
2003-04-18 22:10 ` Nick Orlov [this message]
2003-04-18 22:12 ` 2.5.67-mm4 Christoph Hellwig
2003-04-18 22:29 ` 2.5.67-mm4 Nick Orlov
2003-04-18 23:07 ` 2.5.67-mm4 Nick Orlov
2003-04-19 7:45 ` 2.5.67-mm4 Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-04-18 8:45 2.5.67-mm4 Andrew Morton
2003-04-18 9:17 ` 2.5.67-mm4 Andrei Ivanov
2003-04-18 9:26 ` 2.5.67-mm4 Andrew Morton
2003-04-18 14:31 ` 2.5.67-mm4 Seth Chandler
2003-04-18 15:32 ` 2.5.67-mm4 Andrei Ivanov
2003-04-18 15:49 ` 2.5.67-mm4 Toon van der Pas
2003-04-18 21:48 ` 2.5.67-mm4 Andrew Morton
2003-04-18 23:25 ` 2.5.67-mm4 Nick Piggin
2003-04-19 18:28 ` 2.5.67-mm4 Arador
2003-04-19 21:02 ` 2.5.67-mm4 Andrew Morton
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=20030418221029.GA3956@nikolas \
--to=bugfixer@list.ru \
--cc=akpm@digeo.com \
--cc=andrei.ivanov@ines.ro \
--cc=hch@infradead.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