From: Alan McKinnon <alan.mckinnon@gmail.com>
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 [thread overview]
Message-ID: <200912091743.50847.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20091209152416.GA8387@muc.de>
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
next prev parent reply other threads:[~2009-12-09 15:45 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
2009-12-06 20:45 ` Alan Mackenzie
2009-12-09 15:24 ` Alan Mackenzie
2009-12-09 15:43 ` Alan McKinnon [this message]
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=200912091743.50847.alan.mckinnon@gmail.com \
--to=alan.mckinnon@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