Solved

POP3 on Redhat 9.0

Posted on 2004-09-22
5
347 Views
Last Modified: 2013-12-15
I have recently installed Redhat 9.0  using Sendmail.  I am going to now install POP3(IMAP).  I went to add the package and I guess since I didn't ask for it up front the CD's didn't install it.  I don't know where the CD's we used to install are.  I would like to just download it and install, but I can't find the file on the Net anywhere, what gives.  Can someone give me a link to RH 9.0 IMAP/POP3?

Thanks...

Dave
0
Comment
Question by:lucasdeskywalker
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 40

Expert Comment

by:jlevie
ID: 12127030
0
 

Author Comment

by:lucasdeskywalker
ID: 12128911
Hmmmm....  My RPM manager has stopped working.  The last couple of packages, I had to install the old fashion way with gzip files?  I looked at the directory that you are sending me too and everything is .rpm?  Can you direct me to the .gz or .tar  of the IMAP package?

I think I have everything else that I need working, so I don't feel like I need RPM?  Is everything going that way, the RPM way?  If I were subscribed to Redhats  up2date service would this help me keep these items working?  I am not quite sure why RPM would just quit working anyway?  I haven't  installed that much?  Most of which I installed I grabbed the gzip file or tarball and did it the old fashion way, does this break RPM if I do this?

Do you know where I can find the gzip or tarball for IMAP, RH 9.0.

Thank you again.

Dave
0
 
LVL 40

Accepted Solution

by:
jlevie earned 200 total points
ID: 12129345
> Most of which I installed I grabbed the gzip file or tarball and did it the old fashion way, does this break RPM if I do this?

Not only can that easily break rpm, but it leads to a situation where updates that you might apply will lead to an unstable system. Also installing/upgrading things out of band from sources can lead to unresolvable dependances on other rpm installs or updates. From your description of this system it sounds like you haven't updated it with all of the security & bug fixes, which is a bad thing. And now you can't easily do that.

When using an rpm based system (essentially all linuxen except slackware or debian) one should by preference update or install things via rpm packages. This properly deals with dependancies or conflicts and the rpm database remains a valid representation of what's installed. A side affect of that is that if sonething bad happens to the system there's a good chance that the damage can be identified by an 'rpm -q --verify -a' and the damaged packages reinstalled. You need to be aware that an rpm installation or upgrade of a package only looks at the database contents when resolving dependancies. So if you replace some rpm package from a source distribution without first removing the rpm package a subsequent rpm operation may tell you that you don't have something-version on the system eventhough you can clearly see the files since the rpm database still reflects the old versions of things.

My philosophy is to only install packages via rpm and to limit the packages that I install to be those from the vendor's release. So I'd gladly use a RedHat 9 rpm for something , but wouldn't download and install a later non-redhat copy of a package or a vendor package from a different version of the OS. The only times that I'll install a non-vendor package is when I absolutely must have a package or version that the vendor does not supply. Then I'll build the package from source. But before installing it I'll remove the vendor copy (rpm -e) unless there are too many dependancies to solve. When that happens I'll build the package to install someplace outside of the normal system directories (usually in /opt).

Since you describe this as a new system set up I'd suggest that you backup config and user data, blow everything away and do a clean install. Then install yum or apt and update the system (see http://fedoralegacy.org).  The result will be a maintainable/upgradeable and secure system, which you don't have at present.
0
 

Author Comment

by:lucasdeskywalker
ID: 12137165
Thank you.  We will back this box up and blow it away immediately.  My co-Admin and I are just coming back to Linux administration and being away from it for years.  I am glad to see that the Linux community has adopted something more along the lines of Windows, otherwise I just couldn't see small business ever being able to adopt.  It sure looks alot of headway has been made by the Linux community and Redhat on making things easier and more managable.

Thank you for your time and thought helping us.  We have no problem reformatting and starting over.  I will immediately subscribe to Redhat's service and I will refrain from grabbing anything but RPM's in the future.

Thanks again.

Dave
0
 
LVL 40

Expert Comment

by:jlevie
ID: 12137273
>  I will immediately subscribe to Redhat's service

In that case you'll need to move from the free distributions like RedHat 9 and below or Fedora to RedHat Enterprise Linux. RedHat support of anything other than RHEL ended in May 2004. There is still support for RH 9 & friends via fedoralegacy.org or you could go with Fedora if you must have a free distro.

Personally I've switched all of my servers (and it's a bunch) to RHEL. And we are really pleased with the support, stability, and reliability of it. As a bonus, it tends to be noticably faster that the previous RedHat versions we've run on the same hardware.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Linux 3 59
DB2 9.7 Grant Execute SP 4 61
http response code 3 39
Golang on CentOS / Fedora 2 15
Network Interface Card (NIC) bonding, also known as link aggregation, NIC teaming and trunking, is an important concept to understand and implement in any environment where high availability is of concern. Using this feature, a server administrator …
I am a long time windows user and for me it is normal to have spaces in directory and file names. Changing to Linux I found myself frustrated when I moved my windows data over to my new Linux computer. The problem occurs when at the command line.…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Suggested Courses

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question