qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Friedt <cfriedt@visible-assets.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root?
Date: Fri, 01 Jun 2007 00:06:43 +0200	[thread overview]
Message-ID: <465F46F3.1080700@visible-assets.com> (raw)

Hi everyone,

I've just gotten qemu emulating an arm system on my laptop, which I'm 
hoping to use for cross-compilation. I don't have a disk image to use 
(is there any way to create a disk image from a directory tree??), so 
I'm using NFS instead.

The strange thing is, is that although I specify no_root_squash in my 
/etc/exports (and I've been using NFS for quite a long time successfully 
with other machines), only when I'm using Qemu does the user id of the 
'init' process [0] get remapped to some completely absurd value of 
4294967295.

Has anyone heard of this happening before?

Thanks in advance for any and all responses.

~/Chris

             reply	other threads:[~2007-05-31 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 22:06 Christopher Friedt [this message]
2007-05-31 22:16 ` [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root? Mark Glines
2007-06-01  5:48 ` Rob Landley

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=465F46F3.1080700@visible-assets.com \
    --to=cfriedt@visible-assets.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).