updating using RPM on RedHat
jo...@saratoga.lib.ny.us
2.2.STABLE1 which was available for the ftp RedHat install at
http://metalab.unc.edu at the time.) I also downloaded the source
code so I could build the ncsa_auth program. I would like to keep my
installation current and prefer to use RPMs.
If I upgrade using RPM will everything in my /etc/squid/squid.conf
be preserved and continue to be used or do I have to back things up
and then restore them? Has anyone set up a script to use the rpmfind
program to automatically check for an update? When I ran rpmfind it
found STABLE4, but it didn't find STABLE5. Is there an official RPM
site for the latest release?
Is there any advantage or disadvantage between using the tarball and
the RPM. I know, for example, MySQL says to use the RPM binary
distribution if possible for best performance. Is there and easy
script or make file setting so that the code goes to the same place
regardless? Right now I have everything in /usr and /etc from the
RPM. The tarball wants everything in /usr/local. I am sure that if I
manually went through and tried to make sure all the references to
/usr/local/squid/etc were switched to /etc/squid I would screw it up
completely by missing some. For me this is another reason to stick
with the RPM.
--
Josh Kuperman jo...@saratoga.lib.ny.us
Saratoga Springs Public Library phone (518) 584-7860 x 211
49 Henry St fax (518) 584-7866
Saratoga Springs, NY 12866
Blue Lang
> If I upgrade using RPM will everything in my /etc/squid/squid.conf
> be preserved and continue to be used or do I have to back things up
> and then restore them? Has anyone set up a script to use the rpmfind
if you use rpm --upgrade, old files are generally saved as file.rpmsave..
> program to automatically check for an update? When I ran rpmfind it
> found STABLE4, but it didn't find STABLE5. Is there an official RPM
> site for the latest release?
well, there is a squid-official binary RPM at
http://home.earthlink.net/~intrep/projects/squid/index.html
but that doesn't mean it'll put everything in the same place as your red
hat rpm..
> Is there any advantage or disadvantage between using the tarball and
> the RPM. I know, for example, MySQL says to use the RPM binary
i personally always use the tarball. you know that it is compiled for your
architecture, on your box, and that it will probably always upgrade to the
same paths - because it puts files where the developers intended them to
go. the downside is that it's a small amount more maintenance at install
time, making symlinks and whatnot. Well worth it, IMHO.
> script or make file setting so that the code goes to the same place
> regardless? Right now I have everything in /usr and /etc from the
./configure --help will show you the different switches to set prefixes
for various files. you can also read the red hat patches, if you want to
see what they did to set paths.
> RPM. The tarball wants everything in /usr/local. I am sure that if I
> manually went through and tried to make sure all the references to
> /usr/local/squid/etc were switched to /etc/squid I would screw it up
> completely by missing some. For me this is another reason to stick
> with the RPM.
actually, to me, that's a great reason not to use packages that change
paths. how long will it take your package maintainer (red hat) to build an
rpm for the next version? what if there is a critical patch you need to
apply? etc, etc.
source distributions might SEEM like more work, but in the long run,
they're almost always easier to maintain.
good luck,
--
Blue Lang, Unix Systems Administrator, QSP Inc. - Raleigh, NC
Phone: 919.875.6994
zsh: command not found: fortune
Steve Snyder
>If I upgrade using RPM will everything in my /etc/squid/squid.conf
>be preserved and continue to be used or do I have to back things up
>and then restore them? Has anyone set up a script to use the rpmfind
>program to automatically check for an update? When I ran rpmfind it
>found STABLE4, but it didn't find STABLE5. Is there an official RPM
>site for the latest release?
My recollection is that it preserved my existing squid.conf, but if
you're worried, just copy that file to another name before installing
the updated RPM.
Here's a sorta-kinda official source RPM:
ftp.redhat.com/pub/rawhide/SRPMS/SRPMS/squid-2.2.STABLE5-3.src.rpm
Binaries built from the above source RPM are working great for me on
my RedHat v6.0 system.
*** Steve Snyder ***
Darren Steven
> I installed Squid from the RPMs when I installed RedHat (using
> 2.2.STABLE1 which was available for the ftp RedHat install at
> http://metalab.unc.edu at the time.) I also downloaded the source
> code so I could build the ncsa_auth program. I would like to keep my
> installation current and prefer to use RPMs.
>
> If I upgrade using RPM will everything in my /etc/squid/squid.conf
> be preserved and continue to be used or do I have to back things up
> and then restore them? Has anyone set up a script to use the rpmfind
> program to automatically check for an update? When I ran rpmfind it
> found STABLE4, but it didn't find STABLE5. Is there an official RPM
> site for the latest release?
>
> Is there any advantage or disadvantage between using the tarball and
> the RPM. I know, for example, MySQL says to use the RPM binary
> distribution if possible for best performance. Is there and easy
> script or make file setting so that the code goes to the same place
> regardless? Right now I have everything in /usr and /etc from the
> RPM. The tarball wants everything in /usr/local. I am sure that if I
> manually went through and tried to make sure all the references to
> /usr/local/squid/etc were switched to /etc/squid I would screw it up
> completely by missing some. For me this is another reason to stick
> with the RPM.
I have a custom RPM based on the source RPM that redhat provides for
2.2stable4, but with everything in the usual /usr/local like the squid
tarball. I use the RPM system as we have a number of caches (8+) that we
manage. I like to be able to know exactly what version of squid we have,
how it was built, and be able to make another box exactly the same (or
re-build a given machine). The RPM build gives me a number of binary
rpms that allow me to target certain standard configs, and control what
extras are installed on the box. Upgrading to a new version of squid (eg
2.2S5) means modifying the source RPM SPEC file, as appropriate for the
new sources, building new configs, testing on another box, and then
propogating to the production machines. Learning how to work with RPM
takes a bit, and some extra initial work is required, but for a
production box, it is worth the effort.
--
Darren Steven
Applications Specialist
Networking Tasmania
Telstra Australia
Ph.1800 813 302