Bug 7606 - upgrade to 6.0 installs sendmail
upgrade to 6.0 installs sendmail
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Depends On:
  Show dependency treegraph
Reported: 1999-12-05 15:32 EST by Tim Pepper
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-22 13:37:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Pepper 1999-12-05 15:32:03 EST
I don't use sendmail.  If I use the upgrade option on the RH6.0 cd to
upgrade my older redhat installations, the installer appears to have no
option to not install sendmail.  This means I have to upgrade, uninstall
sendmail, and fix my qmail installation as sendmail's installation causes a
few little problems with it.  It would be really nice if the redhat
installer had the option of leaving other mail daemons in place and not
installing sendmail for those of us who use qmail and other non-sendmail
mail daemons.
Comment 1 Cristian Gafton 2000-02-03 21:30:59 EST
Is sendmail in the base component thesedays?
Comment 2 Tim Pepper 2000-02-04 12:14:59 EST
I don't know if it's a "base component" or not...it just seems to always install
no matter what.  Sendmail doesn't appear in the list of packages that I can
choose to install or not install, although I believe its config files are
listed there and I don't install them.  Nevertheless sendmail installs.  Is that
what a "base component" is...something that is always installed regardless of
setup options?
Comment 3 Jay Turner 2000-02-22 13:37:59 EST
Sendmail is indeed in the base package and therefore will get installed no
matter what.  I have added your request to control whether sendmail gets
installed to a list of feature requests.

Note You need to log in before you can comment on or make changes to this bug.