From: <cbowman@netdoor.com>
To: <blinux-list@redhat.com>
Subject: Re: linux, and audio.
Date: Wed, 28 Nov 2001 05:24:00 -0600 [thread overview]
Message-ID: <200111272327.RAA20177@pike.netdoor.com> (raw)
hi, ok thanks for the info on here. now I understand better. thanks for
shairing that.
charles
On 2001-11-25 blinux-list@redhat.com said:
>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
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
Net-Tamer V 1.11 - Test Drive
next reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
cbowman [this message]
-- strict thread matches above, loose matches on Subject: below --
cbowman
` philwh
` cbowman
` A. R. Vener
` cbowman
` L. C. Robinson
` Bill Gaughan
` Dave Hunt
` A. R. Vener
` Bill Gaughan
` Bill Gaughan
` Luke Davis
` L. C. Robinson
` Brent Harding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200111272327.RAA20177@pike.netdoor.com \
--to=cbowman@netdoor.com \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).