Freeman Liu wrote: > Darren J Moffat wrote: >> 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 ? >> > In this phase, only sadasupport open it by ldi_ interface. And in the > future, both user land applications and > sadasupport will use it. I feel this solution can avoid unexpected > effect as well as make the future migration > smooth.
So in this case there is no userland program that will ever need to open /dev/dsp ? If so then I think the best option is not to create it at all even as /dev/private/dsp. -- Darren J Moffat
