Updating samba package

[barrybyrne]

Hi I have a Redhat Enterprise 3 server with samba installed. I've previously run up2date to update packages, but notice that this won't install latest version of samba. (3.0.20). How do I go about this - I'm not very familiar with Linux packages.

* I have this version: samba-3.0.9-1.3E.2
* Latest on RH up2date is: samba-3.0.9-1.3E.3.i386.rpm
* Would like to update to latest version 3.0.30.

Can I just download the latest rpm from samba.org and install it. There are two directories (7.3 & 9.0) of rpms. Will the 9.0 one be applicable for this system?

Is there a way I can easily roll back to the currently installed package if this causes problems?

Sorry for all the questions, but trying to tread very carefully.

Thanks,

Barry

 

[thedaver]

RH has a long history of NOT keeping up with version numbers as provided by package originators, but they OFTEN DO implement their own subnumbering to note that they've accomodated the necessary patches from one original version to another... Ugh, that's muddy, let's make an example:

SAMBA
v 3.0.1
finds a glitch and fixes it
v 3.0.2

REDHAT
v 3.0.1
applies patch to RH version of samba
v 3.0.1-1

The versions do not always correlate. The best you can do is track specific bugs/patches and see when they hit the most recent RedHat version available.

up2date is your friend on this matter, you need to trust it at this point. DO NOT apply .RPMs from another source, PARTICULARLY for EL!

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/

 

[barrybyrne]

Thanks for the advice.

Another question, would it be possible to build latest samba from source and not overwrite any of the current samba files so I could try this and easily roll back?

Thanks again.

- barry

 

[thedaver]

That would be a poor idea. You can obviously save the configuration files and data, but the installation from the .RPM and from source are not likely to be entirely the same. You risk having multiple, conflicting libraries to root out.

Are you trying to find a particular new functionality or address a particular bug or security exposure? It seems like you're pressing really hard to get to the newest version?!!?

If it's that important, save your configuration files and de-install the RPMs completely. Then you can install - at your own risk! - from source and continue to maintain updates from subsequent source.

I don't find this appealing myself, but your mileage may vary.

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/