Alle 17:06, domenica 29 febbraio 2004, Jeroen van Disseldorp ha scritto:
> On Sunday 29 February 2004 06:00, Jeff Dike wrote:
> > I'm uncertain what the basic implementation should be. If it's a
> > device (i.e. made with mknod), I'm not sure that's usable as a socket
> > because I don't think there are accept/connect methods in the
> > character device ops.
> >
> > If so, that means it needs to be a real socket, and the only room in
> > there that I know of for plugging in random things is to add a new
> > address family.
>
> One thing I'm thinking of: Run a special daemon inside the UML that is
> able to talk to the host. This daemon could talk to the host socket
> directly, or, for obvious security reasons, it could talk to a peer
> daemon on the host.
>
> Comments welcomed.
Yes, this is the first answer I thought about (and since it is not in kernel
space, it is less intrusive). The only problem is communication between the
two daemons - and without any kernel change, we resort only to UML
tty's/ssl's. They can even be connected to host network port (there is telnet
in the middle, but this is simple to solve), even possibly something else.
What is good with tty's, is that to attach them to a host socket you do not
need a kernel thread and everything is much simpler! You implement the
file_ops->read to call the host read on the socket (or recv(), or whatever, I
never studied sockets properly).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
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
|
