linux-um archives
 help / color / mirror / Atom feed
From: "Dave (Bob)" <dave@bob-the-boat.me.uk>
To: Richard Weinberger <richard@sigma-star.at>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] "Couldn't grant pty"
Date: Mon, 14 Jan 2013 20:42:20 +0000	[thread overview]
Message-ID: <50F46DAC.2070609@bob-the-boat.me.uk> (raw)
In-Reply-To: <20130112230654.4462c938@spider.haslach.nod.at>

On 12/01/2013 22:06, Richard Weinberger wrote:
> Am Sat, 12 Jan 2013 18:05:28 +0100 (CET)
> schrieb "Dave Humphreys (Bob)" <dave@bob-the-boat.me.uk>:
>> Richard,
>>
>> In the 64 bit environment (with additional 32 bit glibc) that works,
>> I do: (/uml_test is a mount point for a filesystem)
>>
>> mount --bind /dev /<path_to_32_bit_stuff>/dev
>> mount --bind /proc /<path_to_32_bit_stuff>/proc
>> mount --bind /sys /<path_to_32_bit_stuff>/sys
>> mount --bind /uml_test <path_to_32_bit_stuff>/uml_test
> What about /dev/pts?
> Why the chroot anyways?
>
> Thanks,
> //richard
>
>

Richard,

Well, of course, I was thinking that setting up the bind mount of /dev
took everything else with it. I probably did know better, but it's my
mistake.
Explicitly adding:

mount --bind /dev/pts /<path_to_32_bit_stuff>/dev/pts

Makes everything work. Very sorry guys...

Why chroot?

I have had problems in the past with mixed environments. 

I maintain glibc and uclibc systems in various architectures, and find that keeping everything very separate keeps the confusion levels down.

David



------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel


  reply	other threads:[~2013-01-14 20:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12  9:55 [uml-devel] "Couldn't grant pty" Dave (Bob)
2013-01-12  9:58 ` Richard Weinberger
2013-01-12 12:07   ` Dave Humphreys (Bob)
2013-01-12 12:34     ` Antoine Martin
2013-01-12 14:29       ` Richard Weinberger
2013-01-12 15:52         ` Dave Humphreys (Bob)
2013-01-12 16:00           ` Richard Weinberger
2013-01-12 17:05             ` Dave Humphreys (Bob)
2013-01-12 22:06               ` Richard Weinberger
2013-01-14 20:42                 ` Dave (Bob) [this message]
2013-01-12 18:31   ` [uml-devel] Network related UML Crashing Dave Humphreys (Bob)
2013-01-12 22:11     ` Richard Weinberger

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=50F46DAC.2070609@bob-the-boat.me.uk \
    --to=dave@bob-the-boat.me.uk \
    --cc=richard@sigma-star.at \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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