From: "Oliver Falk" <oliver@linux-kernel.at>
To: "'Jesper Juhl'" <juhl-lkml@dif.dk>, "'Andrew Morton'" <akpm@osdl.org>
Cc: <dan@fullmotions.com>, <linux-kernel@vger.kernel.org>
Subject: RE: SSH and 2.6.9
Date: Fri, 29 Oct 2004 12:52:32 +0200 [thread overview]
Message-ID: <200410291050.i9TAo7Y7025791@pils.linux-kernel.at> (raw)
In-Reply-To: <Pine.LNX.4.61.0410291234530.22050@jjulnx.backbone.dif.dk>
> > Jesper Juhl <juhl-lkml@dif.dk> wrote:
> > >
> > > Now I guess we just need for someone to find out why LEGACY_PTYS
> > > breaks ssh (and other apps?) with kernels >= 2.6.9,
> >
> > Works OK here, witht he latest of everything. Please send
> > the faulty .config.
> >
> > If you could generate the `strace -f' output from good and bad
> > sessions and identify where things went wrong, that would help.
> >
>
> I have no problem here, and I can't reproduce it by enabling
> LEGACY_PTYS either, so you'll have to get the .config and
> strace etc from Danny Brow.
Similar problem occured at my box, but it's not kernel 2.6.9 which breaks
SSH. At leat for me...
If you are running FC3T3, then try to remount /dev. Since some version of
udev obsoletes the dev package and afterwards no /dev/pts/* exists, since
dev is no longer there and udev 'overmounted' /dev...
Best,
Oliver
next prev parent reply other threads:[~2004-10-29 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 19:51 SSH and 2.6.9 Danny Brow
2004-10-27 20:54 ` Jesper Juhl
2004-10-27 21:25 ` Danny Brow
2004-10-27 21:49 ` Danny Brow
2004-10-27 22:36 ` Jesper Juhl
2004-10-28 9:29 ` Andrew Morton
2004-10-29 10:36 ` Jesper Juhl
2004-10-29 10:52 ` Oliver Falk [this message]
2004-10-29 10:55 ` ismail dönmez
2004-10-29 12:45 ` Jesper Juhl
[not found] ` <m3u0sfs0fm.fsf@rajsekar.pc>
2004-10-28 17:44 ` Danny Brow
2004-10-29 12:03 ` Rajsekar
2004-10-27 22:27 ` Danny Brow
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 19:59 Danny Brow
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=200410291050.i9TAo7Y7025791@pils.linux-kernel.at \
--to=oliver@linux-kernel.at \
--cc=akpm@osdl.org \
--cc=dan@fullmotions.com \
--cc=juhl-lkml@dif.dk \
--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