samba - Apr 2010 - Any pitfalls updating straight from 3.0.34 to 3.5.2?

Okay, so I've just put the sernet repo file in my yum.repos.d directory and
a yum update will elevate my samba server to the latest version. Is there any
pitfall that is out there that I can avoid before yum updating.

Centos 5.3
samba3-3.0.34-37 & related packages
openldap-2.3.43-3.el5 & related packages

I still have my samba3-3.0.34 packages squirreled away so I can force downgrade
if I need to, but I don't want to if I don't have to.

Any advice before the plunge?
Ray

Some entries in your smb.conf have changed default values.  Get a listing
from "testparm -v" before and after to be able to work around those
details.


Also, IIRC, With the newer samba 3 packages (starting around 3.3), you need
to have a correctly configured krb5.conf file.


------------------------------------------------------------------------
Tony Hoover, Network Administrator
KSU - Salina, College of Technology and Aviation
(785) 826-2660

"Don't Blend in..."
------------------------------------------------------------------------
 
-----Original Message-----
From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
On Behalf Of ray klassen
Sent: Friday, April 16, 2010 10:46 AM
To: samba at lists.samba.org
Subject: [Samba] Any pitfalls updating straight from 3.0.34 to 3.5.2?

Okay, so I've just put the sernet repo file in my yum.repos.d directory and
a yum update will elevate my samba server to the latest version. Is there
any pitfall that is out there that I can avoid before yum updating.

Centos 5.3
samba3-3.0.34-37 & related packages
openldap-2.3.43-3.el5 & related packages

I still have my samba3-3.0.34 packages squirreled away so I can force
downgrade if I need to, but I don't want to if I don't have to.

Any advice before the plunge?
Ray


      
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

If you're not connecting to an Active Directory (either as a trusted domain,
or as a domain member), configuring Kerberos may not be required.  
If you do require Kerberos,  the [realms] and [domain_realm] sections would
need to be customized for your network.  Additionally, the default_realm
entry in the [libdefaults] section would need to be edited.


------------------------------------------------------------------------
Tony Hoover, Network Administrator
KSU - Salina, College of Technology and Aviation
(785) 826-2660

"Don't Blend in..."
------------------------------------------------------------------------
 
-----Original Message-----
From: ray klassen [mailto:julius_ahenobarbus at yahoo.co.uk] 
Sent: Friday, April 16, 2010 1:04 PM
To: Hoover, Tony
Subject: Re: [Samba] Any pitfalls updating straight from 3.0.34 to 3.5.2?

Wow. Thanks.

Is there any quick way do create a krb5.conf file. (i.e. standard defaults
and so on?)

________________________________

From: "Hoover, Tony" <hoover at sal.ksu.edu>
To: ray klassen <julius_ahenobarbus at yahoo.co.uk>; samba at
lists.samba.org
Sent: Fri, 16 April, 2010 10:00:28
Subject: RE: [Samba] Any pitfalls updating straight from 3.0.34 to 3.5.2?

Some entries in your smb.conf have changed default values.  Get a listing
from "testparm -v" before and after to be able to work around those
details.


Also, IIRC, With the newer samba 3 packages (starting around 3.3), you need
to have a correctly configured krb5.conf file.


------------------------------------------------------------------------
Tony Hoover, Network Administrator
KSU - Salina, College of Technology and Aviation
(785) 826-2660

"Don't Blend in..."
------------------------------------------------------------------------

-----Original Message-----
From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
On Behalf Of ray klassen
Sent: Friday, April 16, 2010 10:46 AM
To: samba at lists.samba.org
Subject: [Samba] Any pitfalls updating straight from 3.0.34 to 3.5.2?

Okay, so I've just put the sernet repo file in my yum.repos.d directory and
a yum update will elevate my samba server to the latest version. Is there
any pitfall that is out there that I can avoid before yum updating.

Centos 5.3
samba3-3.0.34-37 & related packages
openldap-2.3.43-3.el5 & related packages

I still have my samba3-3.0.34 packages squirreled away so I can force
downgrade if I need to, but I don't want to if I don't have to.

Any advice before the plunge?
Ray


      
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba