From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: New user encountering problems
Date: Mon, 25 Sep 2000 06:43:34 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0009250639390.5190-100000@localhost.localdomain> (raw)
In-Reply-To: <20000925191657.A26860@gotss.eu.org>
> Redhat may have more out of the box rpms
> but they often don't behave as you'd expect them to out of the box without
> a bit of tweeking.
This is a bit of an understatement. In fact, a couple times I have had
flashbacks to the evil OS installing a couple things. The assumption that
I want to be like the person they designed the RPM for isn't correct. With
at least one mail transport program out there, you can't fix the problem
with the RPM. You must uninstall the RPM, hunt down a couple config files
left, then configure and compile the way you want things.
While I have found RPM to be handy for some things, others turn to a major
pain.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
Jerry Robinette
` Gorgotek Systems
` Kirk Wood
` Jacob Schmude
` Brent Harding
` Geoff Shang
` Brent Harding
` Jacob Schmude
` Kirk Wood
` Brent Harding
` Jacob Schmude
[not found] ` <Pine.LNX.4.21.0009231155110.1013-100000@localhost.localdom ain>
` Brent Harding
` Victor Tsaran
` Brent Harding
` Victor Tsaran
` Kerry Hoath
` Kirk Wood [this message]
` Victor Tsaran
` Distro discusion Kirk Wood
` Chris Nestrud
` Kirk Wood
` Gene Collins
` Victor Tsaran
` Jacob Schmude
` Brent Harding
` Victor Tsaran
` Brent Harding
` New user encountering problems Brent Harding
` HOWTOs (was Re: New user encountering problems) Jacob Schmude
` New user encountering problems Jacob Schmude
` William F. Acker WB2FLW +1-303-777-8123
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=Pine.LNX.4.21.0009250639390.5190-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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).