Make a swinstall pacakge (Man swpackage). We had to role this out to 30
servers. NFS isn't an option (insecure), so we made swinstall packages.
This also works for archiving purposes, allowing you to place a package into
a directory that can be used at a later date.
__________________________________
Raymond T Sundland
Internet Security Analyst
Internet Infrastructure & Security Group
E-commerce Strategy & Delivery
Phone: 201.703.7256
Email: [EMAIL PROTECTED]
__________________________________
Merck-Medco Managed Care L.L.C.
http://www.merckmedco.com/
| -----Original Message-----
| From: Greg Wooledge [mailto:[EMAIL PROTECTED]]
| Sent: Wednesday, August 08, 2001 8:01 AM
| To: Carla Saldanha
| Cc: [EMAIL PROTECTED]
| Subject: Re: Installing binaries and configuration changes.
|
|
| On Tue, Aug 07, 2001 at 09:09:26PM +0100, Carla Saldanha wrote:
|
| > ./configure
| > make
| > make install
|
| > What should I do in order just to ftp the binaries and
| change the
| > configuration for each system?
|
| The easiest way by far would be to NFS mount the source tree onto
| the target system and run "make install" on each system. That's what
| I did on HP-UX 10.20.
|
| Keep in mind that (at least in OpenSSH 2.5.2p2) the "make
| install" process
| will attempt to write to files in the source tree. Because of this
| silliness, you'll have to make sure the source tree is mounted with
| read/write permissions, and also with root access allowed. (I.e.,
| in /etc/exports, you'll need something like "/my/path
| -root=some.host".)
|
