[Samba] Samba 3.0.26a Available for Download
David C. Rankin
drankinatty at suddenlinkmail.com
Tue Sep 11 22:17:37 GMT 2007
Ed Kasky wrote:
> At 05:24 AM Tuesday, 9/11/2007, Gerald (Jerry) Carter wrote -=>
>> Binary packages will be made available on a volunteer basis at
> Not being as adept at building rpm's as I could be if I had the time to
> learn it, is there any supporting documentation anywhere that describes
> how to go about converting from an rpm install to installing from src?
> Or is it easier/preferred/better to stick with the rpm's and build them
> from the src?
> I know there are opinions on both sides but I wouldn't mind hearing a
> few as I try and decide if I should continue with the rpm on a FC6
> machine or convert to a src install....
> . . . . . . . . . . . . . . . . . .
> Randomly Generated Quote (861 of 1270):
> Nullum magnum ingenium sine mixtura dementiae fuit.
> [There is no great genius without some touch of madness.]
> -- Seneca
Don't throw the baby out with the bathwater!!! Seriously, I prefer
rpm's, but I have servers still running mandriva 2005le and no one has
built rpms for that distro for well over a year. So instead of worrying
about installing some new OS, I simply started building them from
scratch/source. Simple process, you only need to figure out what the
./configure options need to be once and then updates are a breeze.
(1) download the latest samba-rev#.tar.gz;
(2) unzip it with "tar -xzf samba-rev#.tar.gz"
(3) change into the new samba-rev# directory
(4) actually read the README file
(5) cd into the new samba-rev#/source directory
(6) run "sh autogen.sh"
FIGURING OUT THE CONFIGURE OPTIONS
While looking at the output of ./configure --help may be daunting,
unless you have very special needs, the only config options you need are
very straight forward. They are basically limited to:
Where are your samba binaries/libs are stored and where do the
documentation, config, and password files go?
For your binaries and libraries, most of the time it is just a matter
of determining whether they are stored, under /usr/bin, /usr/sbin, and
/usr/lib or someplace else like /usr/local/samba/bin,
/usr/local/samba/sbin and /usr/local/samba/lib? If you look at the path
before the "/bin", "/sbin" and "/lib", that is the "prefix" to where
things go. So logically, ./configure has the primary option of --prefix=
that needs to be set. To get this right, just check (as root)
# which smbclient
# which smbd
That tells you the right "/bin" directory is "/usr/bin" and the right
the right "/sbin" directory is "/usr/sbin". So setting the proper
--prefix= for configure is:
A quick check with ls /usr/lib will confirm that /usr/lib/samba is
there and the proper prefix for the lib directory is also "/usr".
The only other parameters that I found vary from the ./configure
defaults are the "--infodir= " (where the /info documentation files go);
the "--mandir= " (where the man pages go); the "--with-configdir= "
(where the smb.conf file goes) and the "--with-privatedir= " (where the
smbpasswd file goes).
Just check you system and find out. On Mandriva (RedHat type systems)
the documentation lives under the prefix "/usr/share" and the smb.conf
and smbpasswd live under the prefix "/etc/samba". THAT'S IT! That's all
the magic required for a basic setup compile from source!
(of course it is up to you to have the needed c compiler and make
utilities installed on your system)(you can throw in the --target=
option for grins.)
So if you have taken note of the ./configure options discussed above,
your ./configure from source should look like this:
# ./configure --prefix=/usr --infodir=/usr/share --mandir=/usr/share
--with-configdir=/etc/samba --with-privatedir=/etc/samba --target=i686
Or, in a more readable for with line continuations:
# ./configure \
Just execute the ./configure as shown above and wait 3 minutes while
tons of stuff gets printed to the screen. If it completes without
crashing and telling you about an error condition then execute the make
Same as configure, but wait 5 minutes, if it doesn't bomb with errors,
your are ready to install. (./configure and make can be done as normal a
normal user, but the *make install* requires being *root)
# make install
Now restart smbd and nmbd and go check things out. Is everything still
connected?, output of "smbclient -U% -L localhost" report the right
samba version? If nothing is working and you are in a huge panic of "Oh
$4!T what now!!" Don't worry.
Restores the previous samba install and you can now go figure out why
things didn't work as planned. Remember, when writing for help, it helps
to include you OS, smb.conf and a level 10 debug capturing detailed
smbclient -U% -L localhost
Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.26a]
Sharename Type Comment
--------- ---- -------
samba Disk Base Samba Share
office Disk Shared Office Files
rankin Disk Rankin Law Firm PLLC
scans Disk Scanned Images from Copier
allen Disk T Stefan Allen
bertin Disk Darren Bertin
guillory Disk David Guillory
jointcases Disk Joint Client Files
lawtools Disk Case Development - Summation
forms Disk Shared Forms and Briefs
computer Disk Computer Drivers and Software
closed Disk Closed Case Files
pdf-gen Printer PDF Generator (only valid users)
IPC$ IPC IPC Service (Samba Server 3.0.26a)
Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.26a]
BONZA Samba Server 3.0.26a
PROVIDENCE Samba 3.0.25b-0.1.68-1378-SUSE-SL10.0
RANKIN-XP Rankin's Computer
RECEPTION Dell 2400 2.6 GHz
(downloaded, configured, made and installed in less time than it took to
write this mini howto ;-)
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9339 fax
More information about the samba