El 19/09/15 a les 10:59, Samuel Thibault ha escrit:
Instead, you could run a Rump instance with USB mass storage only which
uses libusb as backend rather than its own *HCI driver (but that requires
some coding work as it's currently not implemented ;-))
Indeed. We can however start with an all-in solution before adding
multiplexing.
If you want an all-in solution, a simple way to do this could be to run a
single Rump instance inside a single translator which exposes all of /dev
in Rump namespace somewhere under host /dev hierarchy (e.g. /dev/rump/*).
Then it becomes very easy to select what you want, and no matter what you do
it's always a single Rump instance. For example:
- if you want your /dev/hd1 to be a Rump USB mass storage, a symlink will do.
- if you want raw access to network cards, one could have a translator
which opens /dev/rump/bpf (Berkeley Packet Filter) to capture and inject
packets.
- if you want OSS rather than Sun audio, maybe you'll want a translator which
opens /dev/rump/audio and exports OSS in /dev/audio, /dev/dsp, etc.
--
Robert Millan
