From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.44.254]) by listman.redhat.com (Postfix) with ESMTP id 3F3563EA51 for ; Sun, 25 Nov 2001 18:17:12 -0500 (EST) Received: from mail.redhat.com (mail.redhat.com [199.183.24.239]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id fAPNHCp10222 for ; Sun, 25 Nov 2001 18:17:12 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fAPNHCR30375 for blinux-list@listman.redhat.com; Sun, 25 Nov 2001 18:17:12 -0500 Received: from idscc07.onewest.net (idscc07.onewest.net [199.104.81.26]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id fAPNHBw30370 for ; Sun, 25 Nov 2001 18:17:11 -0500 Received: from rupin.localnet (du10.idfl-222.onewest.net [12.7.222.10]) by idscc07.onewest.net (8.11.3/8.11.3) with ESMTP id fAPNDGW18706 for ; Sun, 25 Nov 2001 16:13:16 -0700 Received: from localhost (lcr@localhost) by rupin.localnet (8.11.6/8.11.6) with ESMTP id fAPNGi709218 for ; Sun, 25 Nov 2001 16:16:44 -0700 Date: Sun, 25 Nov 2001 16:16:43 -0700 (MST) From: "L. C. Robinson" To: Subject: Re: linux, and audio. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com X-Reply-To: List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: On Thu, 22 Nov 2001, cbowman wrote: > ... another question. I haven't ever compiled anything before. There is an excellent tutorial in the Software-Building-HOWTO. You can usually shortcut this just by reading and following the directions in the README that comes with the package. > does this need to be done with all linux software No. You can almost always find an appropriate compiled, easy to install version for your distribution. > and is it hard to do? That depends on the type of user. The average M$ computer user has been trained to expect, and "need" expensive phone support for the simplest of tasks, but if you are reasonably literate, and can read and follow directions, it should pretty easy. You don't need to be a programmer. You will find that most of your effort will then go into learning the many features and capabilities of the average package. Occasionally you may try an alpha or beta package that won't compile on your system. Usually you just wait till the project matures a bit. Tweaking the package, and trying to fix it, usually isn't worth the effort, unless you are into programming, AND have an special interest in that particular project. Open Source projects usually mature very quickly, and you would end up upgrading anyway, in a fairly short time. LCR -- L. C. Robinson reply to no_spam+munged_lcr@onewest.net.invalid People buy MicroShaft for compatibility, but get incompatibility and instability instead. This is award winning "innovation". Find out how MS holds your data hostage with "The *Lens*"; see "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html