[Samba] HOWTO centOS 5.5 samba4 dns dynamic update

Daniel Müller mueller at tropenklinik.de
Mon Jul 26 06:12:33 MDT 2010

This is a guide to test the functions of Samba4 (nothing with Samba 3.X) on
centos 5.5 nothing else.

EDV Daniel Müller

Leitung EDV
Tropenklinik Paul-Lechler-Krankenhaus
Paul-Lechler-Str. 24
72076 Tübingen

Tel.: 07071/206-463, Fax: 07071/206-499
eMail: mueller at tropenklinik.de
Internet: www.tropenklinik.de

-----Ursprüngliche Nachricht-----
Von: Nico Kadel-Garcia [mailto:nkadel at gmail.com] 
Gesendet: Montag, 26. Juli 2010 14:05
An: mueller at tropenklinik.de
Cc: samba at lists.samba.org
Betreff: Re: [Samba] HOWTO centOS 5.5 samba4 dns dynamic update

On Mon, Jul 26, 2010 at 5:34 AM, Daniel Müller <mueller at tropenklinik.de>
> For all,
> after I had several problems  making samba4 working as it should on
> centOs5.5 here is a short guide setting it up to work.
> First of all do not install the bind package coming with centos 5.5!!
> Install needs for samba

Let me slow you down here. While your guide is useful, there are a
couple of important things you're not doing.

* You're building this as a root user. Never do this: Configure your
$HOME/.rpmmacros to set your rpm build directories to include
something like this:
     %_topdir /home/username/rpm

* SRPM's can be rebuilt with the command "rpmbuild --rebuild
filename.src.rpm", which also cleans up the mess in your BUILD and
SOURCES and SPECS subdirectories left behind.

* Recent Fedora RPM's remain an issue to grab on the current CentOS
and RHEL releases, due to the recent change in checksum tools.
Replacing RHEL published components with recent Fedora ones is... a
potential compatibility risk.

* Instead of manually installing Samba and losing all that RPM
component information, Why not review the SRPM's at
http://ftp.sernet.de/pub/samba/3.5/rhel/5/? It's a valuable resource
for leading edge Samba RPM's, and you can rebuild Samba cleanly from
them to install as RPM's, even if you don't care to use the RPM's
there directly. That will report all your build requirements as well,
and save deducing them manually. And it gets you away from replacing

* I love configuring and using "mock" to build my RPM's, to prevent
changes in my development machines libraries from skewing my builds of
important software like Samba.

More information about the samba mailing list