James Carlson wrote:
> Freeman Liu writes:
>
>> James Carlson 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.
>>
>> Do you think it a reasonable approach ?
>>
>
> That'd be fine. Glenn's suggestion (temporarily omitting the /dev
> link) would work as well. That approach requires you to be
> temporarily dependent on the devfs implementation details, while the
> "private_dsp" scheme seems a little simpler. As long as there's a
> plan to avoid inadvertent confusion, I'm happy.
>
>
Why do I see a configure script being written in the near future with a
comment that says....
For some %#$%@ reason Sun calls its dsp device "private_dsp". This
is pretty weird but we can look for it anyway.
