Re: sound through enbd

Dag Sverre Seljebotn <[email protected]> wrote:
> It is exclusive-open, however for servers serving multiple users one
> would like each user to be able to open it exclusively, and have the
> results routed differently (it is a hack really, to overcome the fact

I'm not quite sure if I catch this .. you mean that each new user who
opens the SAME device actually be treated as though they had opened a
DIFFERENT device, all of their own.

Well, that would seem to be the business of some generic kernel layer.
There already are things like that - the way ttys are allocated springs
to mind.

The enbd driver actually does something like that (wrt processes, not
users) in order to figure out which device is being accessed ..  in
2.6.x kernels at least certain operations seem only to be possible on
the device major + n * max_partitions, so the driver works out which
minor they were "really" aimed at by consulting a list of registered
pids.

It would not be difficult to make that work "per user" instead. Just
let the user register. However, it would be difficult to deallocate the
devices - that's no problem when using pids because I just deregister
when the process in question closes.

Would "per process" be enough? Instead of a process specifically
registering for a particular device, I can just let the process ask for
and be given a device.

> Such a thing would be a generic solution for routing the enbd more
> dynamically, and would contribute in solve other problems as well (my
> removable media project etc.). It is probably not within enbd's goals,
> I'm just speculating.

It's fair enough, if I understand you correctly.

Any insight on what the proper format is for /dev/audio :-)? Sox really
is not doing a good job of converting .wav's for me, and it stands to
reason that I am not using the correct format parameters!


Peter