From: Dan Shearer <dan@shearer.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: Cameron Patrick <cameron@patrick.wattle.id.au>,
BlaisorBlade <blaisorblade_spam@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net, miquels@cistron.nl
Subject: Re: [uml-devel] mconsole telinit design, worry about init standards?
Date: Thu, 12 Feb 2004 12:17:25 +1030 [thread overview]
Message-ID: <20040212014725.GV4203@erizo.shearer.org> (raw)
In-Reply-To: <200402120114.i1C1E5ip008500@ccure.user-mode-linux.org>
Jeff,
On Wed, Feb 11, 2004 at 08:14:05PM -0500, Jeff Dike wrote:
> dan@shearer.org said:
> > I've got a rough implementation of an mcsonole telinit command, where
> > mconsole_kern opens /dev/initctl and sends a command to change
> > runlevels.
>
> cameron@patrick.wattle.id.au said:
> > How about having some kind of generic interface to allow the host to
> > access files, send signals, etc inside the VM?
>
> Sorry, but none of these handy things are going into the kernel. If you want
> to run processes, open files, etc, you can do all that from userspace.
Could you tell us what the rules are? At some level we can interact with
the kernel (eg call the c-a-d and halt handlers.) Yet at another we
can't (run processes.) This has to do with how much potential there is
for trouble. Would you be happy with sending signals? If so, even RT
signals, which have a payload? If not, perhaps you could indicate which
class of things you are happy for us to trigger. Perhaps only things
which can be conceptually related to the hardware... so long as we know.
This is part of having a clearer model about what UML is.
> I see the following possibilities:
Yes, the things you propose will work. The bit that we have been trying
to get away from here (in more or less ambitious ways:-) is cooperation
from the UML. I don't mind relying on the UML root being non-hostile (in
many cases that is their right to be relatively hostile if they like,
hosting is that sort of a thing :-) but I want to avoid requiring more
than a tiny minimum above ordinary software intstalled, or better still
nothing at all.
--
Dan Shearer
dan@shearer.org
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&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
next prev parent reply other threads:[~2004-02-12 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 0:37 [uml-devel] mconsole telinit design, worry about init standards? Dan Shearer
2004-02-06 5:42 ` Cameron Patrick
2004-02-07 15:33 ` BlaisorBlade
2004-02-09 0:11 ` Michael Richardson
2004-02-12 1:14 ` Jeff Dike
2004-02-12 1:47 ` Dan Shearer [this message]
2004-02-12 3:49 ` Jeff Dike
2004-02-12 4:40 ` Dan Shearer
2004-02-13 11:03 ` Miquel van Smoorenburg
2004-02-13 11:23 ` Dan Shearer
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=20040212014725.GV4203@erizo.shearer.org \
--to=dan@shearer.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=cameron@patrick.wattle.id.au \
--cc=jdike@addtoit.com \
--cc=miquels@cistron.nl \
--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