From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.util.phx.redhat.com (8.12.10/8.12.10) with ESMTP id i2F069bh015105 for ; Sun, 14 Mar 2004 19:06:09 -0500 Received: (from mail@localhost) by int-mx1.corp.redhat.com (8.11.6/8.11.6) id i2F069u22519 for blinux-list@listman.util.phx.redhat.com; Sun, 14 Mar 2004 19:06:09 -0500 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id i2F069S22515 for ; Sun, 14 Mar 2004 19:06:09 -0500 Received: from server2.shellworld.net (root@ip15.shellworld.net [64.49.204.174]) by mx1.redhat.com (8.12.10/8.12.10) with SMTP id i2F06807008716 for ; Sun, 14 Mar 2004 19:06:08 -0500 Received: from server2.shellworld.net (jdashiel@localhost [127.0.0.1]) by server2.shellworld.net (8.12.10/8.12.8) with ESMTP id i2F066tf009786 for ; Mon, 15 Mar 2004 00:06:06 GMT (envelope-from jdashiel@shellworld.net) Received: from localhost (jdashiel@localhost) by server2.shellworld.net (8.12.10/8.12.8/Submit) with ESMTP id i2F065W7009783 for ; Sun, 14 Mar 2004 19:06:06 -0500 (EST) X-Authentication-Warning: server2.shellworld.net: jdashiel owned process doing -bs Date: Sun, 14 Mar 2004 19:06:05 -0500 (EST) From: Jude DaShiell To: Linux for blind general discussion In-Reply-To: <16468.61135.379283.770470@gargle.gargle.HOWL> Message-ID: References: <16468.61135.379283.770470@gargle.gargle.HOWL> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-RedHat-Spam-Score: -1.524 X-Loop: blinux-list@redhat.com Subject: Re: Yasr and DoubleTalk LT X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.4 Precedence: junk Reply-To: Linux for blind general discussion List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 00:06:10 -0000 Did you build yasr from source tarball? When I had yasr working I found it necessary to do that first. Also, recognize when yasr runs it will run itself in another shell environment on top of whatever current environment you have running. If your system is configured to prevent such things from happening, some security reasons exist for doing this then yasr won't run. Did you ever have your doubletalk lt talking using Linux? If so, have you had it talking as a user other than root? If not, you may have a port permissions problem. Yasr worked on other flavors of Unix before anyone got it working on Linux so it doesn't have any Linux dependencies in the package. This is why it may be necessary for you to do the entire build process on it yourself.