<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.5.4">
</HEAD>
<BODY>
You are confusing what runs on the server and what runs on the thin clients. The thin clients already have the 'daemon' running and watching for NAS sound.<BR>
<BR>
All you do is start up something like audemo and the thin clients do the rest.<BR>
<BR>
Dave<BR>
<BR>
On Mon, 2005-01-31 at 15:58 -0600, Tillman Hodgson wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Howdy folks,</FONT>
<FONT COLOR="#000000">I'm trying to set up nasd to serve audio to an NCD 451 an an IBM Network</FONT>
<FONT COLOR="#000000">Station 1000. The X clients (using X's backwards terminology) is a</FONT>
<FONT COLOR="#000000">generic AMD box running FreeBSD -current (which these days is still</FONT>
<FONT COLOR="#000000">fairly closely related to 5.3-RELEASE).</FONT>
<FONT COLOR="#000000"># nasd -v -d 99 -aa</FONT>
<FONT COLOR="#000000">@(#)Network Audio System Release 1.7</FONT>
<FONT COLOR="#000000">@(#)Network Audio System Release 1.7</FONT>
<FONT COLOR="#000000">AuInitPhysicalDevices();</FONT>
<FONT COLOR="#000000">Init: will close device when finished with stream.</FONT>
<FONT COLOR="#000000">Init: will initialize mixer device options.</FONT>
<FONT COLOR="#000000">openDevice OUT /dev/dsp mode 2</FONT>
<FONT COLOR="#000000">Output open(/dev/dsp) failed: No such file or directory</FONT>
<FONT COLOR="#000000">Fatal server error:</FONT>
<FONT COLOR="#000000">could not create audio connection block info</FONT>
<FONT COLOR="#000000">That makes sense to me: I don't have a /dev/dsp (or a /dev/audio or</FONT>
<FONT COLOR="#000000">anythng ...). You see, I don't have a sound card in the server -- it's</FONT>
<FONT COLOR="#000000">sitting headless in a server room (hooked up to a serial terminal</FONT>
<FONT COLOR="#000000">server).</FONT>
<FONT COLOR="#000000">My goal is to have the thin clients log in to it via XDMCP (which</FONT>
<FONT COLOR="#000000">they're been doing fine for a year now) and run apps that generate audio</FONT>
<FONT COLOR="#000000">streams (like /usr/ports/audio/mpg123 with HAVE_NAS=yes enabled). Those</FONT>
<FONT COLOR="#000000">audio streams would then be sent across to the network to the NAS</FONT>
<FONT COLOR="#000000">clients on the thin clients.</FONT>
<FONT COLOR="#000000">That's my theory, anyway. I was somewhat surprised to see that nasd</FONT>
<FONT COLOR="#000000">wanted an audio device to exist on the server end ... that seemed</FONT>
<FONT COLOR="#000000">somewhat counter to my idea of what it's purpose was. And FreeBSD</FONT>
<FONT COLOR="#000000">-current uses devfs[1], which only creates entries in /dev if the</FONT>
<FONT COLOR="#000000">hardware exists to require said entry.</FONT>
<FONT COLOR="#000000">Am I going about this the right way? Are there any workarounds for cases</FONT>
<FONT COLOR="#000000">where audio hardware (and /dev entries) don't exist on the server end?</FONT>
<FONT COLOR="#000000">-T</FONT>
<FONT COLOR="#000000">1. <A HREF="http://www.freebsd.org/cgi/man.cgi?query=devfs&apropos=0&sektion=0&manpath=FreeBSD+5.3-RELEASE+and+Ports&format=html">http://www.freebsd.org/cgi/man.cgi?query=devfs&apropos=0&sektion=0&manpath=FreeBSD+5.3-RELEASE+and+Ports&format=html</A></FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>