6 messages in net.sourceforge.lists.courier-users[courier-users] Double-checking insta...
FromSent OnAttachments
Lloyd ZusmanApr 29, 2005 4:19 pm 
Sam VarshavchikApr 29, 2005 4:57 pm 
Lloyd ZusmanApr 29, 2005 5:17 pm 
Lloyd ZusmanApr 29, 2005 7:00 pm 
Sam VarshavchikApr 29, 2005 7:30 pm 
Lloyd ZusmanApr 29, 2005 7:58 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Double-checking install scenario.Actions...
From:Lloyd Zusman (lj@asfast.com)
Date:Apr 29, 2005 4:19:53 pm
List:net.sourceforge.lists.courier-users

I'm about to freshly install Courier on a new machine, and I want to make sure that I understand the proper sequence of events. This machine is currently using sendmail, and I want to keep that program up and running for as long as possible before switching over to Courier.

To the best of my understanding, this should be the scenario. If any of you see any flaws in this, could you let me know? Thanks.

1. Use rpmbuild to build a binary rpm for courier-authlib.

2. Do an rpm install of courier-authlib.

3. Use rpmbuld to build a binary rpm for courier.

4. Shut down and disable sendmail.

5. Do an rpm install of courier.

6. Check the courier-authlib and courier configurations, and make any necessary changes.

7. Start up courier.

A question: could I switch the order of steps 2 and 3, or is there some reason for why I should install courier-authlib before building the courier binary rpm?

Thanks in advance.