From: <wlestes@duvallp.uncg.edu>
To: raman@Adobe.COM
Cc: blinux-list@redhat.com
Subject: Re: RealPlayer, RAP, and XVFB
Date: Tue, 30 Jun 1998 18:11:36 -0400 [thread overview]
Message-ID: <199806302211.SAA10159@duvallp.uncg.edu> (raw)
In-Reply-To: <13721.9328.752877.311730@labrador> (raman@Adobe.COM)
> Rather than complaining after simply downloading the
> script, you would be better off with such tools if you:
>
> 1) Looked at the script to see what it does
> --in fact the readme file that comes with rap documents
> exactly what it does--
>
> 2) test and get each individual piece working in your
> environment in this case Xvfb etc
> --there is no valid excuse
> such as "I did not have access" for not doing this--
> because you can start xvfb from any shell running inside
> emacspeak
>
> 3) finally use the packaged rap script so you dont have to repeat all the steps
> each time--
>
> If you are not comfortable with doing this, go use M$
> software where you will have the option of clicking yes, no
> or cancel --
Raman, I agree with you in the attitude and actions that you suggest
linux users should take. That is, that is the attitude I try to bring
to new software under linux (and other OSes i use). However, I would
point out that much of what linux needs to do to be sucessful in the
desktop OS market is provide more of the "yes-no-cancel" features that
many microsoft video games provide. Ultimately, we will have to find a
balance between the "do it yourself because you know your environment"
and "have the computer do it for you because the environment is not
open enough to be known". I suspect that this balance will take some
time to reach and will require much patience on all sides.
--will
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
T. V. Raman
` wlestes [this message]
` Chris Peterson
` T's Mailing Lists
` Brian L. Sellden
` Whistler
` T. V. Raman
` Linux support (was RE: RealPlayer, RAP, and XVFB) Jason White
` RealPlayer, RAP, and XVFB T. V. Raman
` wlestes
` Whistler
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=199806302211.SAA10159@duvallp.uncg.edu \
--to=wlestes@duvallp.uncg.edu \
--cc=blinux-list@redhat.com \
--cc=raman@Adobe.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).