From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NIOjb-00066o-3V for garchives@archives.gentoo.org; Wed, 09 Dec 2009 15:45:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 10503E062B; Wed, 9 Dec 2009 15:45:04 +0000 (UTC) Received: from mail-ew0-f214.google.com (mail-ew0-f214.google.com [209.85.219.214]) by pigeon.gentoo.org (Postfix) with ESMTP id C9D68E062B for ; Wed, 9 Dec 2009 15:45:03 +0000 (UTC) Received: by ewy6 with SMTP id 6so2119126ewy.29 for ; Wed, 09 Dec 2009 07:45:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=WH3NEa1kyGpFnDUhoXnIBfSbKyvXSjbrWOlhXXSg+zM=; b=Tp5IUOx1NZzCd4C2ZIHqprI7rE5hNl4yTryMxfJEgF9vIx4zGZrMXR5w/uQx8InKhW Tm0MqLHFPhuN02dbgASM2iSvgfwtaYXbyQbMej5LiNyWw33vzG3wYi1mwF3n+M7H0kwj uCt0OYFmYCFH4ohe1xUjzXJWC4rfffGfmCd3w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=C6+uNDae9A6OJo2fQOWHwMIwjIghgZdHUm0fdMCreZWn3gSuxAyMBtkxSICMe7U3ju pjoacv4BH2TFCk2VAj+/CQDNKKy1F6qkXqkji2fFSNDv1zN4CYmEccgwSffFPslvpsip phyhwXfcf1fGzKFkkdzXVpqX0j6ZumAEsccjQ= Received: by 10.213.47.9 with SMTP id l9mr1098535ebf.93.1260373502088; Wed, 09 Dec 2009 07:45:02 -0800 (PST) Received: from nazgul.localnet (dustpuppy.is.co.za [196.14.169.11]) by mx.google.com with ESMTPS id 13sm1511414ewy.13.2009.12.09.07.44.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 09 Dec 2009 07:45:00 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems setting up sshd on an installation kernel Date: Wed, 9 Dec 2009 17:43:50 +0200 User-Agent: KMail/1.12.4 (Linux/2.6.31-zen9; KDE/4.3.4; x86_64; ; ) References: <20091206144836.GA2599@muc.de> <20091209152416.GA8387@muc.de> In-Reply-To: <20091209152416.GA8387@muc.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912091743.50847.alan.mckinnon@gmail.com> X-Archives-Salt: 604e2264-2821-4ea6-86ee-80d0fbb8e05e X-Archives-Hash: b7ab86cdab262e4aeeb9af12931bff11 On Wednesday 09 December 2009 17:24:16 Alan Mackenzie wrote: > > 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. > > As said, I fixed the problem by mounting /dev with --rbind. This > misunderstanding cost me, perhaps, 10 hours of my time. > > I then reported my problem to the bug tracker, suggesting that the manual > should be amended to say "--rbind" here. > > I really wish I hadn't bothered. My attempt to contribute was brusquely > brushed aside by somebody who didn't even bother to thank me for my > trouble (I always thank people reporting bugs to my project), said that > he "couldn't reproduce [my] error", and asserted that sshd wasn't meant > to work in the chrooted environment (why on Earth not?), implying it was > my stupid fault for not following the manual rigidly and droidwise. To > cap it all, he patronisingly referred me to the appropriate sections of > the fine manual (that's after my having reported how I'd already fixed > the problem for me). I can see his point of view, the chroot environment is something that exists only while doing the installation and as such is a temporary dodge so that you can do it. No binary distro runs sshd in the chroot it creates while performing the install either. The supported method is to ssh into the "LiveCD" environment then chroot from that shell. It's hard to imagine a scenario where you would have more than one user doing that at the same time, so why run sshd in the chroot at all? > See https://bugs.gentoo.org/show_bug.cgi?id=296073 > > Seems to me, reporting problems to Gentoo is a waste of time, at least > documentation problems. That is a classic case of applying a specific case to the general case. You had a problem with one specific dev regarding one specific bug relating to one specific piece of documentation. To then assert that contributing anything to any aspect of Gentoo documentation is pointless merely on the basis of one experience is disingenuous to say the least. -- alan dot mckinnon at gmail dot com