Freeman Liu wrote:
>> Given that /dev/dsp is a well-known name, and applications are quite
>> likely to find it entirely by accident (for example, by way of
>> ./configure tests), how will it be kept reasonably "private" until
>> you're ready to expose it?
>>   
> 
> Taking these applications into consideration, we can change the name to 
> something else, for example,
> /dev/private_dsp, and it will be found by those applications. As for 
> sadasupport, the change is trivial.
> And sadasupport is the only consumer of this device file in this phase.

Why does is the /dev/ entry needed at all ?  What in userland needs to 
open that /dev/ entry and use it ?

-- 
Darren J Moffat

Reply via email to