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. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
