Hi everybody, I have a client with redhat 3.8 32bits, on this platform he use an old samba version Could you tell me if the new samba's version (Samba 4) can be installed on this platform. Fr?d?ric DOUCHE Groupe APX Vos Architectes ''Services & Technologies'' Mobile:+33.(0)6.98.05.29.85 29 Rue Denis Papin - Parc Club des Pr?s - 59650 Villeneuve D'Ascq [file:///C:\Users\fdouche\AppData\Roaming\Microsoft\Signatures\logo.gif]frederic.douche at apx.fr<mailto:frederic.douche at apx.fr> www.apx.fr<http://www.apx.fr/> ________________________________ Avant d'imprimer ce message, pensez ? la protection de notre environnement.
On Mon, 2012-12-24 at 15:22 +0100, Douche, Frederic wrote:> Hi everybody, > > I have a client with redhat 3.8 32bits, on this platform he use an old samba version > > Could you tell me if the new samba's version (Samba 4) can be installed on this platform.It certainly may be easier to run an older version of Samba than the very newest code, on such an old platform. What features of Samba 4.0 do you need on such an old host? You really should upgrade the host, and not just the Samba installation. We strive to keep Samba running on really old systems, but there are limits. You will however need to work those out yourself by trial and error, as the packages at http://www.enterprisesamba.org/samba-packages/red-hats-rhel/ do not stretch back to RHEL 3.8. As RHEL 3.8 will not have a current python, you may need to either use the install_with_python.sh script, or try the autoconf build in source3/. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org
RHEL 3 I believe reached end of support (by RedHat, not Samba) in 2010. I believe RHEL 4 has since reached end of support as well. So unless the client is paying for RedHat extended life-cycle service or is off the network (unlikely he wants to interface with Samba), he should be off of that platform ASAP because he's no longer receiving any security patches. ----- Original Message ----- From: Douche, Frederic [mailto:Frederic.Douche at apx-integration.fr] Sent: Monday, December 24, 2012 09:22 AM To: samba at lists.samba.org <samba at lists.samba.org> Subject: [Samba] New version Samba matrix Hi everybody, I have a client with redhat 3.8 32bits, on this platform he use an old samba version Could you tell me if the new samba's version (Samba 4) can be installed on this platform. Fr?d?ric DOUCHE Groupe APX Vos Architectes ''Services & Technologies'' Mobile:+33.(0)6.98.05.29.85 29 Rue Denis Papin - Parc Club des Pr?s - 59650 Villeneuve D'Ascq [file:///C:\Users\fdouche\AppData\Roaming\Microsoft\Signatures\logo.gif]frederic.douche at apx.fr<mailto:frederic.douche at apx.fr> www.apx.fr<http://www.apx.fr/> ________________________________ Avant d'imprimer ce message, pensez ? la protection de notre environnement. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
On Mon, Dec 24, 2012 at 9:22 AM, Douche, Frederic <Frederic.Douche at apx-integration.fr> wrote:> Hi everybody, > > I have a client with redhat 3.8 32bits, on this platform he use an old samba versionAs an active RHEL user and CentOS and Scientific Linux user, I've got to tell you, nothing should be *allowed* to run on such an old system. Production suport for RHEL 3 ended in 2010, there is extended support available until January 30, 2014, but it's going to stink to be you trying to maintain that platform, especially since security updates have fallen well behind. EPEL has dropped support for it, the "mock" toolkit for building RPM's cleanly has even dropped support for RHEL 4, Amazingly, rpmforge is still doing some updates for RHEL 3, but system components will be in the rpmforge "extras" repository, so you'll have to dig around for them. Tools like "rsync" will benefite from the RPMforge update. If you need it, you can try my SRPM components for Samba 3.6.10 at https://github.com/nkadel/samba-3.6.10-srpm. But of course getting *git* to work on RHEL 3.x will be an adventure, itself, and don't even ask about other source control systems like Subversion. I'm the current author of the latest Subversion RPM's for RPMforge, for Subversion 1.6.x and Subversion 1.7.x I'd really encourage you to update to RHEL 5, which is current and maintained, or RHEL 6, which is the current release.
Apparently Analagous Threads
- /dev/tty only on a new container
- MAX PRI for single server (was: Not enoughlinesavailable for Asterisk implemetation)
- Plotting by factor with xts
- Cannot connect to the existing LXC containers (console)
- Is it possible to have 2 WIN servers on the same network?