Samba 3.6 Released With SMB2 Support
Jeremy Allison - Sam wrote in to let us know the Samba project has made a major new release. The main highlight is support for SMB 2.0 which was released as part of Windows Vista. There are a number of other improvements to printing support, clustering, and identity mapping; details can be found in the release notes.
I love playing as the Princess since she can float.
For the first time in 13 or so years, I'm not admining a samba instance at home or work. Recently killed off the last samba share at home due to some VLAN changes. Mounted filesystems all go over the AFS, or the netatalk. I don't do the "vista" and microsoft thing in general, so that doesn't matter. The macs tolerate the AFS and love the netatalk. The PCs actually work flawlessly as AFS clients, much better than in years past. The unix boxes all use the trinity of AFS / kerberos / ldap, and pretty much, always have used that. Samba, wheres that go, in this picture?
Is there any reason to move back? or light up a new Samba so I could.... ummm
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
Now we just need someone to update rdesktop to make use of the new Remote Desktop features of Windows Vista.
There is so much Microsoft Bashing going on that projects like Samba tend to get pushed off as "One of those" Project that only support the Evil Microsoft by Conforming to their standards, vs. trying to make Microsoft Better support ours.
But I have found in Real Life, these tools greatly help increase the usage of Open Source systems. As well deminishes the need to use Microsoft Standards. As you setup you Samba Share and a NFS share (or whatever you want to use) that goes to the same files, you allow your organization to move away from those windows desktops.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Microsoft contributes to Samba and sees it as a necessary product. For mindlessly evil patent abuse, please visit your local Apple store, thanks.
SMB2 communications occur when you have a Windows Vista (and above) communicating with Server 2008. If you're using XP or Server 2003 in any combination with the newer OS, it steps down to SMB1. The thing to realize is that SMB2 doesn't handle oplocks well. So legacy file-based databases will break and become corrupted when communicating over SMB2.
I can't find the KB, but per Microsoft, they highly recommend using SQL and not files for future databases as SMB2 will most likely break that functionality. I can vouch for this advice as I've seen some strange shit in this regard.
Life is not for the lazy.
We've handled that case since the mid 1990's...
Jeremy.