From: Blaisorblade <blaisorblade@yahoo.it>
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: Fri, 29 Apr 2005 21:16:29 +0200 [thread overview]
Message-ID: <200504292116.30483.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200504262123.44365.rob@landley.net>
On Wednesday 27 April 2005 03:23, Rob Landley wrote:
> On Saturday 23 April 2005 08:57 am, Blaisorblade wrote:
> > > 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.
> >
> > Not sure about this... you'll need to be root anyway to chroot, so you
> > can also (bind)mount what you need inside the chroot and unmount it
> > later.
> Hmmm. You're right, that's sucks.
> I've also been thinking about some kind of wrapper that would be root, set
> up the environment, and run UML as a non-priviledged child process.
> Working out the details is a bit tough, though...
>
> > You
> > still need to ask UML to do this, yes, but it's different (also you could
> > even provide a simple module to load to do this, if the other ideas are
> > rejected at any level).
>
> Hmmm... I suppose I could always have a wrapper script
which can't be setuid if in bash, could if in Perl and perlsuid is installed.
> that runs UML as a
> non-root process in the chroot environment and opens a named pipe that we
> can write into via hostfs when we want the chroot environment depopulated.
No, that must be a regular file... Linux does not pass requests to work on
device nodes, named pipes, sockets down to the filesystem, so none of them
can pass datas between the machines. You'd need a real IP socket (TCP/UDP),,
or maybe something mconsole-based.
You can pass the location through a normal assignment on the cmd.line (which
will become a env.var, or you might parse /proc/cmdline).
> (I vaguely recall there's a way to tell UML where to drop its memory
> file...)
Setting TMPDIR.
> Better not to modify UML at all, if possible...
>
> Rob
--
Paolo Giarrusso, aka Blaisorblade
Skype user "PaoloGiarrusso"
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-04-28 18:08 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 [this message]
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
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=200504292116.30483.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--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