Samba: Less Important Because Windows Is Less Important
Jeremy Allison - Sam writes "Interview Bruce Byfield did with me after the Samba 4.0 release. Discusses interactions with Microsoft, the future of the code and project, and many other things."
Still important :-P
"When information is power, privacy is freedom" - Jah-Wren Ryel
Earlier today I read a man complaining to Slashdot that Linux only has two data sharing options "off" and "configure 400 settings." He was answerred with a post of "just use Samba."
And then, this.
Samba is a dance. Your confusing it with the term "Sambo" which is generally considered a racist term.
http://en.wikipedia.org/wiki/Samba_(disambiguation)
So, integrating old machines running legacy systems with newer/different platform servers is less important?
Funny, I thought Sambo was a martial art. -- http://en.wikipedia.org/wiki/Sambo_%28martial_art%29
Unsurprisingly... ;)
http://code.google.com/p/chromium/issues/detail?id=160570
Really makes Chrome devices a pain in the ass when it comes to network shares. :/
Back in the 80's, I used to meet up with friends at the local Sambo's Restaurant. However, to maintain Political Correctness, we always referred to it as "Jigaboo's".
It's funny - laugh.
Actually, I wouldn't be surprised if the latest versions of the SMB protocol were a bit more asynchronous and high-performance. But using older versions, I found SMB (Samba on one end, CIFS on the other, in general), could not saturate a gigabit ethernet link, while NFS and AFP could. I kept using it because for compatibility but stuck with NFS or AFP for performance, AFP more now that Netatalk 3.x sucks so much less than Netatalk 2.x. (Netatalk 2.x suffered from various problems like random connection drops.)
In Spanish, especially in conquered Latin America, zambo was one of the (many) technical terms used to specify the different mixes resulting from white (Spanish), native american, and blacks, and their descendants. Specifically, zambo(a) was the first generation of the mix between native american and black.
It's current usage is obviously broader and informal, and no longer a "racist" term per se.
Thinking that Samba is less important because "Windows is less important" is definitely off target. The obvious implication of the statement is that if Samba is less important then NFS is. I certainly am not aware of any trend there. CIFS and NFS both remain valid NAS protocols. To the extent that "Windows is less important" because PCs are less important then you are dealing with some serious trends in storage.
.
One trend is the growing use of virtual disks in VMs to provide storage. This is just stupidity. Shared files server users far better than virtual disks do. Files are not created for OSs, they are a mechanism for sharing information between users.
The other trend is away from NAS and towards object storage. That is a good trend, but not one that will make NAS protocols obsolete anytime soon.
Samba is a dance.
Yes. And when we let Microsoft lead, they keep stepping on everyone's toes. I'm going to a friend's office soon to find out why the addition of one stinking Windows 8 system has broken all the file sharing between her existing Vista, Windows 7 and XP systems.
Have gnu, will travel.
I had it in my career too. Back in the mid-90s, Linux was used sparingly in certain industries and Windows dominated the workplace. To survive, Linux systems did almost always have to play ball.
That balance *has* changed, but not quite that much, though perception of what is going on is very very contingent on career path. About 2003 or so, I was going from place to place with significant Linux footprint, but unavoidable Windows instances. As my experience progressed, opportunities that I pursued afforded me the chance to gravitate to nearly Linux exclusive businesses and organizations. If you are a top notch Linux developer, your reality will change so that Windows will not be a large role.
In relatively recent history, my career has had me participate in more wider sampling of companies with significantly complex IT organizations, despite my recent Linux-exclusive career. I realized that while *my* world had changed, the business world at large was still where it was about 7 years ago with respect to Windows footprint.
Particularly someone as renouned as Allison is likely to have his world changed for more than typical...
Offtopic, but Interesting. There is a brazillian music group called Sambo who replays famous music in Samba rythm.
https://www.youtube.com/watch?v=o95cSuXlsdk
https://www.youtube.com/watch?v=NK1YY9l8vDQ
Maybe it didn't.. maybe she just told you it did so that you'd go to her office after hours. Ever think about that?
Real life is funnier than jokes, you know in some parts of the country there is still a chain of restaurants called Bojangles. I shit you not, look it up.
I support the Slashcott and will not be reading or commenting from 2/10/14 to 2/17/14. Beta is steaming pile of dog shit
I thought Sambos turned into Denny's.
I drank what? -- Socrates
SMB exists in the corpoare environment only so this is a non issue outside the office.
Eh? Most consumer grade NAS on the marker are accessed via SMB (and run Samba on Linux).
The name on its own is not racist. The company is pretty decent. The guy himself was a great dancer and quite famous. Might as well start calling people Cosby or Chappelle to somehow be derogatory. I would guess it is the same as calling native-americans Chief or Indians calling white guys boss.
Samba is less important because windows is more open. Other than hosting cifs shares there is now little you can't do in the server room without Samba. Samba certainly makes things easier in that as others have pointed out "it just works". The fact is today AD is at the core the identity system many enterprises use.
The good news is that with nss_ldap, the mit kerberos package and little else you are off to the races now. It takes a little setup Samba would do for you, but a couple cron jobs to keep kerb TGTs refreshed, some thought about your ldap config, perhaps and AD schema extention or two and you have got what you need.
Its nothing like the bad old days of trying to participate in an NT domain. Its not great Microsoft has played fast and loose with some standards but AD is open enough that foreign clients can participate without specifically designed compatibility layers like Samba.
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
In our office we have a 2 TB NAS for backing up desktops and posting files that need to be shared to the whole office. Guess what it runs? Linux + samba + a custom web interface. The fun thing about SAMBA these days is that a lot of people running it don't realize they are running it.
If you've got a small enough organization, you can probably get by with gmail tied to your domain and either dropbox or serverless CIFS for sharing files.
I'm talking about Main-Street businesses. Not Wall Street businesses.
Look around you for pete sake. Business does not begin with GM and end at the NYSE.
Sig Battery depleted. Reverting to safe mode.
This should be an easy battle. Make sure he can only use linux on his workstation : )
http://soylentnews.org/~tibman
Give him a breakdown of licensing and support costs for the next 5 years. Windows Server gets pretty expensive when you start adding the client acces licenses in for all of the different products.
SMB exists in the corpoare environment only so this is a non issue outside the office.
Say what? I was under the impression that file sharing between PCs running Windows on the same LAN used the SMB protocol.
Windows Servers are serving business clients.
Not always. There used to be Windows Home Server.
windows isnt important ever again
Have him explain, in technical terms, how what samba provides isn't real. If by it not being real he means "not AD-based", then well, samba 4 is the answer he's looking for. Learn samba4, port ldap data (if you use ldap), start it on a test server (rename the domain to something else!), log in from various versions of windows, test, then deploy and be done. I'll be doing it in the coming weeks: migrating from samba3+ldap to samba4. The dreaded old HP printers are my only nightmare, their print drivers are broken and don't work properly even with windows servers :(
A successful API design takes a mixture of software design and pedagogy.
It could probably be translated to "cohabitation partner". The legal term "sambo" refers to each of two people living together as a couple in a long-term relationship with a shared economy (like they were married). So simply sharing an apartment would not qualify from a legal perspective. (This is for example relevant if one of them were to die.)
I thought Sambos turned into Denny's.
Like the tiger turned into butter?
They can take my LifeAlert pendant when they pry it from my cold dead fingers.
It's a biscuits'n'gravy place. I do have to ask what's wrong with "Bojangles", though. You do know it was Bill Robinson's nickname, right? If that's racist, then so is "Coolio" or "Dr. Dre".
Gamingmuseum.com: Give your 3D accelerator a rest.
I don't understand. Samba and Windows Server have practically identical features. You should be able to mount a Windows share the same way you mount a Samba share.
Give me Classic Slashdot or give me death!
An operation like that may just as likely be using a Unix based appliance. Even for small businesses, server components are no longer Windows only. In some case, the client side of the vertical apps aren't Windows only anymore either.
A Pirate and a Puritan look the same on a balance sheet.
Interview Bruce Byfield did with me after the Samba 4.0 release.
Next week, Hulk interview Steve Ballmer. Goodnight puny humans!
systemd is Roko's Basilisk.
or is it still at the alpha release?
There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
No, Sampo was a magic item in the Kalevela that brought fortune to its holder.
Picture Rachel McLish, but blond.
maybe she just told you it did so that you'd go to her office after hours. Ever think about that?
Except for her husband. Picture Dolph Lundgren, with normal hair. And glasses. I'd never pick on someone wearing glasses. I'm just a nice guy that way.
Have gnu, will travel.
Oh sure. The mail slot interface is an essential part of the protocol. That's why you just can't buy Samba based products anymore, all commercial NAS are re-badged versions of Windows server.
Sarcasm, in case anyone was wondering..
Jeremy
Actually we use the term Sambo for a Fish round here
http://en.wikipedia.org/wiki/Samson_fish
Hmm, please ignore my post :). Reading some other comments I realize it is totally wrong...
In the world of industrial automation, windows unfortunately seems to reign supreme. Just about every development environment for PLC and PAC controllers is windows and .Net based. And as of late, PC based automation (think PC based PLC/PAC) is becoming more popular and guess what is the primary platform? Windows. You might be thinking "How the hell can windows be used in a hard real-time application?" Well it is possible and the first time I ever saw it was in the Aerotech A3200 platform. Its a pretty neat CNC motion control platform which uses a Windows PC networked via fire wire to what they call intelligent drives. The software installs an RTX server (then from Ardence) which is given full hard real-time access to the 1394 adapter. The server runs the core motion control/automation kernel, Windows cant mask any of the interrupts which would cause "jitter" and delay on the 1394 bus. Not sure who else uses it but there has to be more. Beckhoff makes a lot of automation hardware that is all PC based and they offer their own automation software suite. Its all .Net Windows XPE, 7 and CE based and fully integrated into Visual studio. Kontron offers Linux support for their ThinkIO system but its roll your own. Not that its bad but in Automation, ease of development is crucial to timely delivery of a system. I don't want to sound overly dramatic but Windows and .Net has become a cancer in the industrial automation world. Maybe cancer is too strong a word, drug might be more appropriate. Visual studio and .Net along with C# is quite alluring to companies looking to build a large automation system with the least amount of programming effort. Even the big players like Allen Bradley and Siemens all have Windows only software. Sure maybe some of it can run under WINE but that isn't the point here.
I have yet to see any automation company make any effort to offer a real soup-to-nuts Linux based automation platform that doesn't require you to roll your own C/C++ code (if someone does please let me know). There is EPICS which is used on many particle accelerators but I still cant figure out how to use it. The only partial exception is Opto22 who's SnapPAC hardware controller runs Linux. But their PC automation control software is Windows only as well as their Development, configuration and HMI tools.
Linux also lacks big CAD/CAM names like Solid Works, Autocad, BobCAD/CAM and even Ashlar Vellum. However, most of them offer OSX versions but its not Linux. Thankfully, FreeCAD looks to be the most promising FOSS CAD application along with PyCAM for converting the CAD models to G code for CNC machines.
Pretty much every Linux/Samba-based NAS on the market has the same policy limitations as a desktop Linux installation.
Plus, the mailslot interface is a very important part of the protocol. It's how networked users have been able to communicate with one another for quite a long time, without needing third-party software, which also provides an interface for applications to also do so across machines. The reason it was likely never fully implemented on Linux is because there is no reasonable way to implement it, given the lack of any kind of standardization (particularly in the GUI). Literally the only thing available, after 20 years, is Linpopup, which basically doesn't really even work anymore anyway. And there's no proper interface to take advantage of mailslot functionality to make anything better. RealPopup is a very good WinPopup replacement on Windows, with quite a bit of configurability, but it's completely unable to communicate with a Samba-based machine in its native mode.
So, what options does that leave us with? 1) A cross-platform internet-reliant instant messenger service, full of ads and spam and regular updates. 2) A local server-based chat application, requiring configuration of both a server and clients, and also requiring aforementioned server which severs all network communications if that machine is down. 3) Something Bonjour-based, all of which are typically extremely bloated and require installing garbage Apple software on a PC to communicate.
That means all of the Linux-based machines I use have no way of communicating with Windows users on the network, meaning I have to always have a Windows PC as well, because there is no reasonable alternative.
That's typical of a lot of NAS boxes::
e.g. Zytel NAS
http://www.trustedreviews.com/zyxel-nsa325_Peripheral_review
They're running on ARM chips typically (low idle power yet fast performance). All linux with Samba.
In fact, I don't think I've ever run into a NAS box that was running Windows. Servers yes, but NAS?
There are plenty of comments below about the racistness of 'sambo', but I have no idea as to what it's about.
Non-Linux Penguins ?
it's also 9 points in scrabble!
... Jabber?
You're making a problem out of nothing to make an (invalid) point.
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
That being said, I'd MUCH rather use something that's better documented. SAMBA is used on all sorts of linux enabled media servers and the fact of the matter is it does not always work. Especially with other systems that are trying to implement SMB/CIFS like my Mac (no longer SAMBA from Apple) or media servers with differing versions of SAMBA the result is often buggy or something not working at all.
(which is not to say that GP doesn't have it's own 'interesting' failure modes)
And you're attempting to downplay serious lacks of policy and communication support in an attempt to disregard the point.
The fact that businesses use what they use proves my point.
Jeremy,
Since you're hanging about, let me take the opportunity to say thanks for making such a vital, useful and wonderful piece of software - and thanks to the rest of the Samba team, too.
I've used it at work over the decades, I use it at home even now. It's made my life better. That is not at all hyperbole.
I know that this is Slashdot, but it wouldn't hurt to say thanks, right?
Cheers!
I usually react to ad integration by switching to a different program . . .
hawk