[EMAIL PROTECTED] said:
> Hmm, how would it work? Guest user opens /dev/xyz. UML discovers
> that the major-minor combination should be passed through. It opens
> (as the executing user's self) /dev/xyz on the host, receives a host
> FD, and makes a control block accessible via the guest FD, which it
> passes back to the client. The client now does read-write-ioctl-close
> on that FD, and UML does the same syscall with the same arguments, on
> the host. Voila.
You're describing a pass-through driver. Implement a driver which implements
its ops in terms of the underlying host device. Register it in place of the
usual random driver, and you're good to go. This is really the right way
to fix this problem.
Jeff
-------------------------------------------------------
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_ide95&alloc_id396&op=click
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
