From: Joshua Murphy <poisonbl@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Problems setting up sshd on an installation kernel
Date: Thu, 10 Dec 2009 11:52:59 -0500 [thread overview]
Message-ID: <c30988c30912100852x19b595dav49e75bc64df998a0@mail.gmail.com> (raw)
In-Reply-To: <20091210152706.GA31654@princeton.edu>
On Thu, Dec 10, 2009 at 10:27 AM, Willie Wong <wwong@math.princeton.edu> wrote:
> On Thu, Dec 10, 2009 at 10:36:41AM +0000, Penguin Lover Alan Mackenzie squawked:
>> How did this breakage happen? I would guess that at the time the
>> installation procedure was devised, this line
>>
>> # mount -o bind /dev /mnt/gentoo/dev
>>
>> worked perfectly OK, since /dev didn't have any subdirectories. Some
>> time recently, /dev acquired subdirectories (e.g. /dev/pts), but nobody
>> realised this would render the chrooted system less capable.
>
> Just to be pedantic.
>
> Not subdirectories. 'mount --bind' binds the directory tree. What /dev
> picked up was submounts, which is why you issued 'mount --rbind' as a
> workaround. (The mount manpage I think has something about devpts.)
>
> I wonder if 'mount -t devpts devpts /dev/pts' is a better workaround
> for your problem, though.
>
> Cheers,
>
> W
>
> --
> M: Hot almond milk. Best stuff on earth.
> Sortir en Pantoufles: up 1098 days, 14:03
That one only works if the kernel of your install disk is configured
to allow multiple instances of devpts to be mounted
(CONFIG_DEVPTS_MULTIPLE_INSTANCES) ... I'm in no way certain if that's
enabled on the Gentoo generated livecds, currently.
--
Poison [BLX]
Joshua M. Murphy
next prev parent reply other threads:[~2009-12-10 16:54 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
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 [this message]
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=c30988c30912100852x19b595dav49e75bc64df998a0@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