Slashdot Mirror
Samba 3 By Example
Samba 3 By Example begins on a very friendly note by explaining how to get the most out of it any what you'll need to complete the exercises in the rest of the book. The beginning also includes a Windows networking primer, complete with packet captures (using the popular tool 'ethereal') showing how network browsing really works, under the hood.
This book follows the evolution of a fictitious company, "Abmas", through an impossible growth from a 9-person office to a 2000-person network with multiple sites around the world. You assume the role of the IT guy: charged with growing the company's network infrastructure, planning for change and, above all, keeping the users happy.
Some of the major challenges tackled in this book are:
- Using Samba-3 as an NT-4 style PDC
- Using Samba-3 as an domain member server
- Using the various authentication backends as alternatives to the traditional 'smbpasswd' backend
- Using LDAP to implement a Samba-3 PDC with backup domain controllers
- Authentication using winbindd
- Migrating from NT-4 to Samba-3 for a PDC
- Using kerberos to integrate Samba-3 into a Microsoft Active Directory domain (as a domain member server)
I am extremely impressed by Terpstra's book. It addresses the complete spectrum of Samba deployments, from the 10-person office to the 2000-seat, multi-site enterprise while explaining not just what to do, but how to do it and, most importantly, why. The examples are practical and you can really imagine some poor sap^H^H^H^H^H^H^H^H unfortunate systems administrator finding him/herself in these very positions. This book says that these scenarios are hypothetical aggregations of real-world situations, but could swear I've worked for this company before.
One of the nicest things about this book is that each situation is followed by a Q&A section - almost like a textbook - that addresses both the important points of the exercise, as well as some of the trivial details that were left out for the sake of brevity. Don't be tempted to skip them thinking that it's just a rehash.
It's worth noting that this book is not a replacement for TOSHARG and defers to it for technical details in multiple cases. These two books should be sidearms for any IT administrator that has to deal with Windows clients on a daily basis.
I'm also very impressed with Terpstra's candor about Samba's features, weaknesses and road map. Nowhere in this book is Windows put down as inferior or is Samba touted as the "be-all, end-all" of Desktop and client management solutions. The relative flexibility of Active Directory and Samba is discussed only briefly and the choice to use Samba over Windows is ultimately left to the reader. Since you've gone to the trouble of purchasing this book, Terpstra assumes you've already made up your mind and require no further convincing.
Continuing to be mindful of office politics, Terpstra devotes a section in each chapter to the political implications of replacing Windows with an open source product, and an entire chapter to the issues inherent in bringing Samba into a traditionally Windows-based shop. Even though he refers to this chapter as a "shameless self-promotion of Samba-3", I found it to be an even-handed discussion of the issues you will most likely encounter from anti-Unix advocates and IT managers who have bought into the anti-Linux FUD. These are real issues that Systems Administrators need to know how to deal with effectively but too many of us simply dismiss because we feel they are uninformed.
In addition to examples of Samba configuration, examples are provided to integrate Samba with other useful servers such as the squid web proxy, OpenLDAP, bind and dhcpd. The configuration files for Samba as well as these additional pieces of software are also conveniently located on the included CD-ROM, along with Samba 3.0.2 packages for Red Hat Fedora Core 1 and SuSE Linux (Enterprise server 8 for x86 and s390 and SuSE Linux 9).
I think my biggest complaint with this book is that the "case study"-like format of this book tends to lump a large number of new features into a single example. This can make it hard to isolate the particular feature that you're interested in.
For instance, the example that illustrates automatic printer driver downloads to Windows clients is lumped into a chapter that is primarily concerned with using LDAP to implement a BDC. Automatic driver installation is a great feature that many sites far too small to consider implementing LDAP would likely be interested in.
In all, though, I'm extremely pleased with Samba 3 by Example - perhaps even more than TOSHARG. In it, you'll find plenty of tips, working examples and honest admissions of bugs (and their workarounds) that will keep you from losing your sanity. You could almost call this book a 300 page Samba and Windows networking consultant with over 8 years of experience. Terpstra has been incredibly kind to the Samba community by imparting so much wisdom to us all in this book.
Josh Malone has been a FreeBSD and Windows system administrator for three and a half years working in development shops and hosting companies, and currently works as a Linux engineer for an embedded systems company. You can purchase Samba 3 By Example from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page
Cool, I've always wanted to learn how to samba.
True story.
Samba is probably one of the largest driving forces enabling people to migrate away from windows servers. It's a cornerstone of lots of offices that I have visited.
MP3 Search Engine
So does Samba-3 support the "trade secret" PAC information that Microsoft inserted into their Kerberos tickets (to great consternation of the Kerberos community)?
It's a free, robust, easy to admin file server and DC with impeccable reliability.
KARMA TAG! You're it.
after my first experience with samba (opposed to windows 2k server) i was highly enthousiastic but being one of the lesser linux geeks around i had some difficulty setting it up.
overall my impression is that in total i suppose you would need less time to set up and maintain a nice samba server than a w2k server, even if it is your first time installing linux.
with the help of this book it will become even simpler....
yay.
Show a man some news, distract him for an hour. Show a man some mod points, distract him for the rest of his life.
bookpool.com
Obviously teaching things by example is not new, but far too many computer books on too many subjects (especially programming) don't use enough examples to illustrate their points. Some just use poor examples.
Samba is one of those setups where the total amount of functionality is far more than many users need, so a collection of well-designed examples will greatly speed one's implementation (and reduce common security problems). Fortunately the default config file has improved in Samba to the point where it's not too difficult to setup basic printer/filesystem sharing.
These "cookbook" style books obviously can't replace a reference, but they often are more useful as a starting point. I've spent over five years on unix systems now, but I still groan at the lack of examples in the man pages of more obscure command line software. Google often comes through, provided I can think of a good phrase that describes what I'm trying to do ("search and replace with perl command line" - perl -pi -e 's/searchterm/replaceterm/g' [filenames], btw).
"The universe seems neither benign nor hostile, merely indifferent." --Carl Sagan
I have limited Samba experience, but have found that my 5-box home network became much more stable after allowing Samba to become a browse master. We had occasional issues with printers dropping offline, files copyable one direction but not another, odd hangs where the only solution was a power-off reset, bringing boxes up in sequence.
Once I installed Samba on my main OpenBSD server, things quieted down. Took a few weeks before I realized: no Windows "hiccups" had happened! It's stayed that way for months now. I may have gotten the same effect by setting up a Windows PDC, but I don't have a "dedicated" box new enough to be useful for that. At this point, even if I don't need the shares, I'll leave it running just to stabilize the wife's WinME box!
I have found Samba very workable and not too hard to set up. At first I only thought of Samba as a hack to interoperate with Windows and assumed NFS was better. But over a few years I've had a number of troubles with NFS, from timeouts to UID translation to large file support (on Linux - I'm sure NFS is better on Solaris!) Finally I realized that Samba is not just a scab, it works fine and is easy to set up. Now I use it even to network Linux boxes. Sure Samba's guts might be messy but it doesn't seem to hurt anything.
Yes, and at the recent FOSE expo in DC the Apple guy that was standing under the sign in the Apple booth that said "LDAP and Kerberos" showed me how easy it was to use.
It uses all the normal Apple GUI type controls which basically take care of all of the configuration changes to smb.conf and krb5.conf. Basically a slick "apple looking" configuration file editor. I thought SWAT made samba configuration pretty easy, but this Apple stuff is great. Really cool stuff.
This book is currently available through The Register's bookshop with 30% off to UK readers.
I've got a fever and the only prescription is more COBOL.
http://www.oreilly.com/catalog/samba2/book/toc.htm l
"I just completed a three day training course based on this book. Every example just worked fine. The explanations are great but you do need the "Samba-3 Howto and Reference Guide" for detailed background information...."
That's funny, i just completed a google search for your "comment" here and gues what i found?
VERBATIM COPY
Interesting.
Well, it does until you start using a lot of Excel spreadsheets which link to other spreadsheets on a Samba share at least. Then you start to see serious locking problems.
;-(
Believe me, I've been banging my head against this for a couple of weeks now (I can't reproduce the problem, but other people on the network can and do, daily). Everyone seems to have their own idea about the correct combination of oplocks, level 2 oplocks, veto oplocks, deadtime etc to use; but nothing seems 100% foolproof. This is the reason we're probably going to be switching away from Samba to Win2k3. I don't want this, but as the only Linux guy, it's hard to fight the tide when you're having to clear down the locks and force people to close and re-open files almost daily as they're lock out of their own files...
Code, Hardware, stuff like that.
You mean like the 229
Seriously...I don't know what Linux distro you're using......I've heard this comment before, and out of the few dozen I've tried, nothing ever stored configuration information in more than two places:
1)
2) hidden directories in the user's home directory, for personal configuration files, rather than system-wide.
Anything that's in the user's home directory is set by the interface of whatever program they're running, though, so you hardly need to 'search out and edit' files that are in 'various different formats'.
If you're going to spread FUD, at least spread something that's true.
Oh...wait.....that would mean it wouldn't be FUD, wouldn't it?
"City hall" in German is "Rathaus" Kinda explains a few things......
Of course you'll want to RTFM on those commands first so you know what you're letting yourself in for.
I don't know the specifics of your situation, so this very well may be an extremely bad idea for you, hence the "RTFM" comment.
The system these configuration entries came from is a server that hosts numerous files which many people read, but only one or two people need to write to (and only one of those on a regular basis).
The problem being that the annoying win32 program being used refuses to function unless it believes it has exclusive read and write access to the files, even though it never actually writes to the files (in most cases).
It¦s not an elegant solution, but it solved the problem here with no ill effects since it was installed over a year ago, but yes, it has huge potential to cause file corruption on a system where the same files are concurrently modified by multiple users.
However, that's going to change. There is already support for RPC security when using NFSv4 in Linux 2.6. That way, you can use Kerberos authentication and encryption for your NFS exports, and all is well. It's still marked as experimental, but I suspect it to be mature before long.
All that already works on Solaris, of course.
A better way to do it would be to only veto oplocks on certain types of files with the veto oplock files option.
/*.DBF/*.dbf/*.CDX/*.cdx/*.IDX/*.idx/*.fxp/*.FXP/* .prg/*.PRG/*.mmo/*.MMO/
We had problems with dbase file locking until we vetoed oplocks on those files.
To do it, it looks like this:
veto oplock files =
This way, you're not using oplocks on only the types of files that are giving you hell, while getting the best performance possible from all other file types.
Guys,
I committed the entire text of the book to the public samba-docs code tree on April 5th. We are having some difficulty in building the PDF file on the Samba build system. This will be resolved as soon as possible.
We are committed to open information about open source software. Please be a little patient with us, you will get your candy soon.
Cheers,
John T.