public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Murphy <poisonbl@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems setting up sshd on an installation kernel
Date: Sun, 6 Dec 2009 13:56:06 -0500	[thread overview]
Message-ID: <c30988c30912061056i5ae1c3cco179f47e50eb905a2@mail.gmail.com> (raw)
In-Reply-To: <4B1BE2D4.3090001@f_philipp.fastmail.net>

On Sun, Dec 6, 2009 at 11:59 AM, Florian Philipp
<lists@f_philipp.fastmail.net> wrote:
> Alan Mackenzie schrieb:
>> Hi, folks!
>>
>> I'm trying to get sshd working on an embryonic Gentoo installation on my
>> laptop.  The reason is that I want to ssh from my nice comfy desktop
>> system into this laptop to do the rest of the installation stuff.
>>
>> The installation kernel with which I'm having problems is:
>> Linux livecd 2.6.30-gentoo-r8 #1 SMP Tue Nov 3 11:40:51 UTC 2009.
>>
>> Having started sshd on my laptop, when I do
>>
>>     ssh -lroot 192.168.2.101
>>
>> from my desktop, I get prompted for my ssh key's pass phrase, which I
>> enter.  Thereafter, nothing happens, and it continues to happen for a
>> long, long time.
>>
> [...]
>>
>> Clearly openpty (a C function) is failing to find some file.  Don't you
>> just love error messages like "No such file or directory" which forget
>> to identify the filename?  I'm guessing that the file it can't find is
>> the device file for the new pty.
>>
>> Is there anything I can do to get sshd working from this kernel (and if
>> so, what?), or is there something fundamentally wrong with the kernel
>> configuration?
>>
>
> Where did you start sshd, in the chrooted environment or on the live cd
> itself?

My first thought as well... I'd guess, just at a glance, that sshd was
started in the chroot, and that /mnt/gentoo/dev/ is bind mounted
properly, but /mnt/gentoo/dev/pts/ isn't.

-- 
Poison [BLX]
Joshua M. Murphy



  reply	other threads:[~2009-12-06 20:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 14:48 [gentoo-user] Problems setting up sshd on an installation kernel Alan Mackenzie
2009-12-06 16:28 ` Mick
2009-12-06 20:23   ` Alan Mackenzie
2009-12-06 22:22     ` Mick
2009-12-06 16:59 ` Florian Philipp
2009-12-06 18:56   ` Joshua Murphy [this message]
2009-12-06 20:45     ` Alan Mackenzie
2009-12-09 15:24     ` Alan Mackenzie
2009-12-09 15:43       ` Alan McKinnon
2009-12-09 16:46         ` Alan Mackenzie
2009-12-09 19:42           ` Alan McKinnon
2009-12-09 21:57             ` Stroller
2009-12-09 22:20               ` Alan McKinnon
2009-12-10 10:36               ` Alan Mackenzie
2009-12-10 14:23                 ` Neil Bothwick
2009-12-10 18:41                   ` William Hubbs
2009-12-10 20:42                   ` Mick
2009-12-10 15:27                 ` Willie Wong
2009-12-10 16:52                   ` Joshua Murphy
2009-12-09 22:35             ` Alan Mackenzie
2009-12-10  5:00               ` Stroller
2009-12-09 21:27           ` Stroller
2009-12-10  0:23             ` Dale
2009-12-06 20:17   ` Alan Mackenzie
2009-12-06 18:36 ` Walter Dnes
2009-12-06 21:31   ` Joshua Murphy
2009-12-06 21:49     ` Boy Hartsuiker

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=c30988c30912061056i5ae1c3cco179f47e50eb905a2@mail.gmail.com \
    --to=poisonbl@gmail.com \
    --cc=gentoo-user@lists.gentoo.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