linux-um archives
 help / color / mirror / Atom feed
From: Henrik Nordstrom <uml@hno.marasystems.com>
To: Rob Landley <rob@landley.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] The source to that firmware-uml thing is now up...
Date: Mon, 25 Apr 2005 01:20:54 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0504250115250.28792@filer.marasystems.com> (raw)
In-Reply-To: <200504200606.06828.rob@landley.net>

On Wed, 20 Apr 2005, Rob Landley wrote:

> By the way, I've toyed with the idea of running this sucker in an otherwise
> empty chroot environment (/proc/self/fd is likely to exist and have fairly
> uninteresting contents.  As a chroot environment, it just has symlinks that
> point to nothing), but to chroot the UML kernel process from inside the
> initramfs, I need to come up with a new syscall.

Not neccesarily. All you need is a way of making the UML execute the 
chroot syscall. This can be easily be done by loading a module, or even 
linking a dummy object file with just a kernel init function making the 
chroot call if it is not sensitive when in the kernel boot process this 
takes place.

> Can't do it before running the UML kernel because A) it needs to make 
> its memory file, 2) it needs to access /proc/self/exe, III) it needs to 
> loopback mount its executable file to pull the trick I just did.

Ok, then the module approach is the simplest.

> Does a new "chroot UML" syscall sound like a worthwhile idea?

IMHO a syscall is overkill for this.

Regards
Henrik



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      parent reply	other threads:[~2005-04-24 23:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 10:06 [uml-devel] The source to that firmware-uml thing is now up Rob Landley
2005-04-23 12:57 ` Blaisorblade
2005-04-27  1:23   ` Rob Landley
2005-04-29 19:16     ` Blaisorblade
2005-04-28 23:38       ` Rob Landley
2005-05-01 11:06         ` Blaisorblade
2005-05-02  5:14           ` Rob Landley
2005-05-02 19:38             ` Blaisorblade
2005-04-24 23:20 ` Henrik Nordstrom [this message]

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=Pine.LNX.4.61.0504250115250.28792@filer.marasystems.com \
    --to=uml@hno.marasystems.com \
    --cc=rob@landley.net \
    --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