All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Richard Weinberger <richard@nod.at>,
	Richard Weinberger <richard.weinberger@gmail.com>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails
Date: Tue, 10 Mar 2015 15:38:43 +0100	[thread overview]
Message-ID: <54FF01F3.5060203@gmx.de> (raw)
In-Reply-To: <54FCD0DB.4060308@nod.at>

On 03/08/2015 11:44 PM, Richard Weinberger wrote:
> Okay. Does it work on a regular host system?
> I.e. not broken^Whardened.
> 
> I run x86 UML's very often on x86_64...

Ok, I have here just a hardened system, so I'll look for issues related to that .

-- 
Toralf
pgp key: 7B1A 07F4 EC82 0F90 D4C2  8936 872A E508 0076 E94E


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
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:[~2015-03-10 14:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 21:13 [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails Toralf Förster
2015-03-08 21:38 ` Richard Weinberger
2015-03-08 22:40   ` Toralf Förster
2015-03-08 22:44     ` Richard Weinberger
2015-03-10 14:38       ` Toralf Förster [this message]
2015-03-10 14:46         ` Richard Weinberger
2015-03-10 15:11           ` Toralf Förster
2015-03-10 15:49             ` Richard Weinberger
2015-03-10 17:43               ` Toralf Förster
2015-03-10 17:53                 ` Richard Weinberger
2015-03-10 18:24                   ` Toralf Förster
2015-03-10 18:33                     ` Richard Weinberger
2015-03-10 18:39                       ` Toralf Förster
2015-03-10 18:43                         ` Richard Weinberger
2015-03-10 18:56                           ` Toralf Förster
2015-03-10 21:21                             ` Richard Weinberger
2015-03-13 13:40                               ` Toralf Förster
2015-03-13 14:31                                 ` Richard Weinberger
2015-03-15 10:54                                   ` Toralf Förster
2015-03-15 10:59                                     ` Richard Weinberger
2015-03-15 11:29                                       ` Toralf Förster
2015-03-15 11:27                                     ` Richard Weinberger
2015-03-15 12:07                                       ` Toralf Förster
2015-03-15 12:42                                         ` Richard Weinberger
2015-03-15 14:36                                         ` Richard Weinberger
2015-03-15 16:51                                           ` Toralf Förster
2015-03-15 16:56                                             ` Richard Weinberger
2015-03-16 13:23                                               ` Toralf Förster
2015-03-21 22:27                                                 ` Richard Weinberger
2015-03-22 11:05                                                   ` Toralf Förster
2015-03-22 20:50                                                   ` Toralf Förster
2015-03-13 17:01                                 ` 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=54FF01F3.5060203@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@nod.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.