From: "Chris Peterson" <chrisp@citilink.com>
To: <blinux-list@redhat.com>
Subject: RE: RealPlayer, RAP, and XVFB
Date: Wed, 1 Jul 1998 08:08:23 -0500 [thread overview]
Message-ID: <000201bda4f1$53a2e560$0f0962d1@chrispet> (raw)
In-Reply-To: <199806302211.SAA10159@duvallp.uncg.edu>
> If you are not comfortable with doing this, go use M$
> software where you will have the option of clicking yes, no
> or cancel --
While I don't totally disagree with this attitude, I would like to remind
you that, if we want linux to even begin to compete with M$, we need to
provide some mechanism of support. Telling someone to "rtfm" in so many
words is basically saying that, if you're not an expert then we don't want
you. Any customer service rep, telling this to a customer, would have been
fired on the spot.
Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
T. V. Raman
` wlestes
` Chris Peterson [this message]
` 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='000201bda4f1$53a2e560$0f0962d1@chrispet' \
--to=chrisp@citilink.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).