MS getting rid of SAMBA? 475
BenRussoUSA writes "In this ZDNet story . Brian Behlendorf of Apache, Jeremy Allison of SAMBA, Miguel de Icaza of Ximian and now MONO and Eric Allman of Sendmail are all quoted in a story regarding a nasty rumor. Microsoft may be planning to include a Microsoft patented technology at a crucial interoperability point in .NET and maybe the next version of CIFS. Could this spell the end of SAMBA?"
Hmm (Score:5, Interesting)
Re:Hmm (Score:2)
Clients are good for lock-in, Servers bad. (Score:5, Interesting)
Microsoft must be overjoyed that Mac OS X.1 and Linux and Unix all have popular SMB clients. Woo hoo! Desktops of all kinds are locking in the value of having a nice Microsoft-controlled backoffice.
It's the servers of SMB which are the thorn in Microsoft's side. A decent Samba server runs on Linux just fine, which robs Microsoft of all that wonderful lock-in. A Microsoft backoffice solution can be replaced with a drop-in equivalent, and not one desktop user even notices the difference (except there's fewer i.t. emails out to the organization about downtime).
Every time a fully functional drop-in replacement is possible, Microsoft will attempt to change the game to break that possibility. Desktops are hard to replace fully, because every single user has to make a very personal commitment (either by paycheck or choice) to learn all the little differences. Servers are easy to replace without much hardship, and Microsoft knows this. Hence, .net and kerberos tweaks and other closed or extended standards.
And MSIE will break on Apache.... (Score:3, Insightful)
If they actually tried to do this, the effect would be akin to the results if they tried to change MSIE to break on Apache servers (to create pressure to switch to IIS). Even before Code Red, very few sites would switch from Apache to IIS. Making the browser break on Apache would break so many sites that it would not force servers to switch to IIS, it would force users to switch from MSIE.
Likewise, if some future version of Windows breaks Samba, IT managers would simply insist on the old versions of Windows until they found a workaround, e.g., third-party SMB drivers for the "improved" Windows on new systems. Or they would investigate whether it's cheaper, and less risky, to convert every single workstation to Linux than to try, again, to port their key application to run on Windows. Combined with the other major headaches MS is trying to force down IT's staff (e.g., some early reports that the "new and improved" licenses sometimes go *poof* without warning, but it can take days to arrange a replacement. If that happens at the wrong moment, a company could lose a contract or a court case, costing millions of dollars. Are you willing to bet your company - and your personal savings - that Windows will never barf on you?) and this could be the straw that finally breaks the camel's back.
If I had to guess what's happening, MS is floating a trial balloon. They won't pay attention to us, but if InfoWorld starts reporting on the rumors and has some Fortune 500 IT managers saying they'll seriously evaluate alternatives if Samba is locked out of a latter-day CIFS, we'll never hear of this idea again.
What about our own samba protocol variant (Score:2, Insightful)
But will MS really break backwards compatibility? (Score:2, Insightful)
When NT started using encrypted password, there was a registry tweak [runet.edu], which enabled Samba to function.
A real danger seems like it would be MS starting to enforce their patents. It even looks like
Not A Good thing, since much of the Samba development takes place in Australia.
Re:Compatibility will be maintained at some level (Score:2)
> upgrade", which coincidentally breaks Samba.
Sigh. What do you think Windows 2000 did ? Why do you think we had to get Samba 2.2.1 out as soon as we did ? What do you think Windows XP is planning *right now* (search the Samba lists for the new breakage in XP... it's not hard to find).
They do this *EVERY RELEASE*.
This is what it means to be on a Microsoft treadmill. I want to warn the Ximian/Mono folks not to get into the same situation that we're in.....
Regards,
Jeremy Allison,
Samba Team.
I saw this on National Geographic (Score:5, Funny)
They can take my SAMBA (Score:5, Insightful)
Really, what can they do? ECMA rules say they have to licence is "non prejudiciously", and usually that means a percentage of revenues, not a flat fee. So if Jeremy Allison has to send them 20% of whatever he charges for SAMBA, they'll have to accept that.
Re:They can take my SAMBA (Score:3, Informative)
Ironic side note:
This, I recall, is exactly what MS did to Spyglass. When Spyglass sued MS for not paying agreed-to royalties on Internet Explorer, MS responded that the royalties on a product that they sold for $0 was $0. One more company screwed by MS.
I found the password / .NET patent! (Score:5, Informative)
Which will be used only defensively. (Score:4, Informative)
Here's a link to the full text [164.195.100.11] of the patent. But according to the article, "Microsoft does not have to disclose any patents on .Net technologies, unless it is not willing to license them in a nondiscriminatory fashion." And a "nondiscriminatory fashion" toward Ximian Inc would probably involve a royalty-free license. IOW, Microsoft will probably do its usual routine of "We won't sue you over our patents on this technology if you don't sue us over your patents on this technology" in the white paper, as it has done for the FAT specification.
Hypocrite. (Score:2)
CmdrTaco on 08:36 PM August 6th, 2001
Guess that only applies to Star Wars, but not to anything really important. Good thing he isn't a REAL journalist.
Backward compability (Score:4, Insightful)
They threw out NTLM, in came Kerberos
They threw out WINS, in came DDNS
I wouldn't worry too much yet...
That just horrible. (Score:2)
Ben Franklin and Thomas Jefferson just turned over in their graves.
Monopolies (even when they are introduced by the government) always hurt the market. Just look at Wall St. We should look at different rewards for patents than monopolies.
Pure Speculation (Score:5, Insightful)
Considering that to really wipe out samba, microsoft would have to destroy interoperability with previous windows versions... I think this article is just more zdnet sensationalist journalism.
Re:Pure Speculation (Score:2)
And you think they'll balk at that why exactly? Not only will they not have a problem with it, they seem to be actively doing so as an incentive to get people to upgrade. Witness the number of times they've changed file formats in Word for no apparent reason. And how they refuse to backport useful bits to previous versions of Windows (USB support being a good example).
Has Microsoft ever enforced a patent? (Score:2)
Re:Pure Speculation (Score:5, Informative)
It's not "sensationalist jounalism", though. Charlie is trying to make an important point which I will discuss below.
The reason I spoke about it at all is that my personal feelings are that implementing *NEW* Microsoft-revisioned protocols is a waste of people's time. Once they've become a de-facto standard, like SMB, then we have no choice but to try and implement them, just in the same way that Abiword, StarOffice and KWord have to load Microsoft Word file formats.
But to start implementing new Microsoft designed protocols and *help* them become ubiquitous is insane. All IMHO of course.
I don't think Microsoft is planning to wipe out Samba and it is sheer paranoia to speculate on that point.
Jeremy Allison,
Samba Team.
But where does one draw the line? (Score:2)
But where do you draw the line on when to start? How ubiquitous is ubiquitous enough? Is it a good idea to have a project underway so that that you have a bit of a jump start if the protocol does start taking off? Or is it better to wait until the protocol is extremely ubiquitous, and then your Linux servers are at a disadvantage for two or three years until the projects reach maturity?
These are all difficult questions, and the answers may depend on timing. When Samba was started, Linux was still a small player in the server market, and in fact Samba was one of the things that spurred Linux in to popularity. Now that many users and businesses depend on Linux servers, it will probably mean that there will be higher expectations that protocols be supported sooner.
Is it a waste of time to start such a project before a protocol becmoes ubiquitous? I suppose it depend on the ultimate outcome. It is a risk, and life is full of risks. The downside is that some people will have wasted their time (and maybe some money) if the protocol flops. But the upside could be the success of Linux in another server market if the protocol proves to be popular.
Ovbiously there's no easy answer, and I agree that implementing *all* MS standards willy-nilly is probably unproductive, and that implementing MS standards before they become ubiquitous involves some risk. Not all risk taking is bad, however, and if the potential upside is large, I'm not sure I would call it insane.
The end of SAMBA? (Score:3, Funny)
Very likely, but... (Score:2, Insightful)
I doubt microsoft can ignore all these systems. People will not easily dump their workstations for NT...
Re:Very likely, but... (Score:5, Insightful)
Re:Very likely, but... (Score:2, Insightful)
How long did it take them to pay attention to their own customers and get rid of clippy? Four years? How long did it take them to write an SMTP server that allows for conditional relaying like everyone else instead of all open or all closed relaying? Oh wait; they haven't done that yet.
This is closer to an admittance by Microsoft that other systems exist, and they are unwelcome interlopers in an M$-centric network. Leaving the old LAN Manager authentication in, using the same file sharing technology for years, M$ basically didn't see the need to change anything because, after all, no one was using anything but M$ products, right?
So with a step like this, M$ is saying "We know you're not using our products everywhere, so we're going to try to come up with another way to make you pay for our lousy tech".
So now we need a robust file sharing system that works like SMB/NFS/etc from a web browser - cross platform joyousness for the client, apache on whateveryouwant for the server....
--mandi
Re:Very likely, but... (Score:2)
Yeah, but most people are using Windows and NT on their workstations. This is actually to SAMBA's advantage as is the recent anti-trust actions. Microsoft has been held to have market power in desktop OS software, so their ability to enforce their patents has been weakened (intellectual propertly law does not grant one immunity from anti-trust law).
I would not worry about it for now.
This begs the question (Score:5, Insightful)
Gee thanks. (Score:2)
If you understood what I was getting at then why can't you comment? I love your bitchy attitude, PLEASE don't think about what was asked,EVER. Do try and rip the questioner a new one for not dotting his i's and crossing his T's. Thinking about the question is obviously a too great a strain.
Perhaps next time make an intelligent comment on the question ASKED and then in a PS suggest a different language usage.
Re:[OT] Re:Gee thanks. (Score:2)
Ever heard of Walt Whiteman? His grammer was awful. His language was considered sub-par and many an enlightened person considered his work rubbish. Those enlightened people are long forgotten, but Mr. Whiteman's work lives on. In fact I recall a previous US president gives a copy of "Leaves of Grass" to his girlfriends. (I'm no Walt Whiteman, nor am I implying such. I'm pointing out that content and ideas relayed are what's important, especially in such an informal place as /.)
So, when you originally are challenging the reader to think of something "intelligent" before replying, we are to presume that you put your full intelligence into the question?
Shouldn't you have said "when you originally challenged the reader...."? Isn't this sentence considered an overly verbose sentence (or whatever your English teacher calls these things)?
Aren't posts about grammer instead of the topic stupid, idiodic and pointless?
Pay attention now sparky; I'm going to rephrase the question, and let us see if you can follow.
For those that missed out .NET initiative?"
The question I asked was "Should the open source community try and copy or imitate the
What I was hoping for was some sort of semi-thought out response along the lines of "Yes, the open source community needs to or should develop a .NET because X Y Z" or "No the open source community shouldn't because of P D Q".
Thank You
Re:[OT] Re:Gee thanks. (Score:2)
The humor is intentional I assure you. Glad you enjoy it as much as I.
A solution for the DOJ (Score:2, Insightful)
This whould allow Microsoft to "innovate" as much as they want but allow competition by allowing others to freely clone their products & technologies.
Of course MS would complain "Waaah they are taking away our property and giving it to others!". They would be right in a way, but it's not like they they took away Bill's wonderful home or something.
Shows why the patent law is broken (Score:2)
So the licencing wouldn't be prohibitive if you knew you only had to pay it for a limited time within the lifetime of the technology. Copyrights are supposed to help the inventor, but open up the forum to royalty-free competition while the invention is still viable and useful. This would foster more participants in the arena of competing technologies, and thus, more innovation. And we wouldn't be wondering if Microsoft ringing the death knell for SAMBA.
All of which is not withstanding the scary idea that developing a technology for 'changing passwords' should not entitle you to more royalty payments than a developer, of a technology which only wants to
Frightening.
US Patent Office: Selling monopoly rights to common sense for over 25 years. [thinkgeek.com] (Yes, I own the tee-shirt.)
I would be very surprised to see this happen. (Score:5, Insightful)
The reason this would be hard to stomach is that Microsoft has major customers including banks and other data farms which use Samba across their worldwide networks. Microsoft might be a major behometh and may attempt to stifle Project Mono but I doubt it would be throught the form of changing CIFS (the new version of SMB for those who don't know).
Microsoft is a bully and we will always have things to overcome however they still answer to some people, namely their major customers and when they bark orders, Microsoft listens.
Plus, the story doesn't really even talk about Microsoft changing CIFS, it talks about possible patents in
-davidu
Re:I would be very surprised to see this happen. (Score:2)
Replace the word, SAMBA, with java in the above comment. Do you know any "major customers" that have any investment in java?
Re:I would be very surprised to see this happen. (Score:5, Funny)
They should have called it "CIFLS", pronounced "syphilis". Perhaps the 'L' can be implied. "First I got Mono, but then I realized that I also got CIFLS in the same transaction."
Re:I would be very surprised to see this happen. (Score:2)
Based on the above information, I guess this means they'll have to rename SAMBA.
My nomination for a new name: CIFiliS
Re:I would be very surprised to see this happen. (Score:2)
The article does *NOT* say that... (Score:4, Insightful)
It's just a general discussion about patents and how they might impact an Open Source project. They use Samba as an example, but are primarily referring to
Hey Mr. Taco... Read the article next time before posting a comment about it.
Superscary. (Score:2, Interesting)
Wow. Who'd have guessed that it'd be game, set, match already?
Re:Superscary. (Score:2)
Comment removed (Score:3, Insightful)
Does MS control Windows filesharing? (Score:2)
How well could they do it (Score:2, Funny)
and Windows 2000. Of course they could always supply "patches" for NT 4.0 and W2k that will "allow" them to use the new password protocol. But my favorite solution is to host the project in a country were patents do not matter. Let's say Russia.
not disclosing patents to standard bodies? (Score:5, Informative)
Is this true? Consider this article from Fortune about Rambus [fortune.com], in which they were dinged for not disclosing a patent to a standards committee.
The article mentions that Sun and Dell got in trouble for similar things, and had to license the patents royalty-free. Dell had a patent on VL-BUS technology, and Sun had one on DRAMs for SparcStations that Kingston complained about. The Dell story (from 1996) is summarized here [gtwassociates.com] and this is from the FTC [ftc.gov], while the Sun case (from this year) is mentioned here [ebnews.com] and here [ebnews.com].
- adam
Fight fire with fire (Score:2)
This is going to be the only way that free software will win.
move to development non US (Score:3, Insightful)
why not put it in international waters and work on it from wherever you want ?
this goes back to cryptonomicon CAVE idea
more and more things like this are going to happen we should simply wake up and put them out of reach of poloitical ideas and companys
what are the problems with this approach ?
reagrds
john jones
Re:move to development non US (Score:4, Informative)
This is how harmfull laws are passed without the will of citizens who are eitheir too ignorant to act or too weak to have their voices heard. No wonder you have more and more activism in Worlds Summit like it happened in Genova (Italy).
Re:move to development non US (Score:2)
doesn't matter, at least in the case of patents. dmca is another issue.
patents require registration in the country where they're applied.
that means that if M$ holds a valid U.S. patent, they can forbid you from using the process in the U.S.
you can avoid this patent by moving to a country where the patent has not been registered. That's how Zimmerman got around the RSA patents.
even if that country later on recognizes software patents, it can't register them retroactively. that's a universal precept of patent law.
'course, if people use your infringing product in a country where the patent is valid, they're facing potential liability themselves. that's why PGP was illegal to import into the U.S. for a long time.
US kinda like MS? (Score:2)
Re:move to development non US (Score:2, Insightful)
Re:move to development non US (Score:4, Insightful)
US law even apparently applies to Russian soil. Just ask Dmitry Sklyarov. The US gov't believes its law applies worldwide. And Russia isn't screaming blooddy murder about it! (Why not?!)
No one is safe, unless perhaps they decide to NEVER visit the US ever again. Even that might not be enough, just look at Manuel Noriega. Kidnapped by the US in a miltary raid and imprisoned in a US jail.
And the US would be very likely to bomb any rig out in international waters. We'd justify its destruction and the killing of its workers by saying we were protecting the US economy from economic terrorism and all our sheep/citizens will bleat their approval. And with it having been in international waters, we wouldn't be in trouble with any other country for violating its sovereignty.
Not that international law has ever (in practice) ever applied to the US ... just look at how many treaties we violate.
Re:move to development non US (Score:2)
wow, too many x-files episodes buddy.
you can't be arrested for violating patent law. not even in the United States. it's purely civil. you can only be sued by the patentholders. so what's happening to Dmitry can't happen when you're talking patents.
Re:move to development non US (Score:2)
Just like Americans can be and are arrested in foreign countries for breaking the laws of those countries.
The DMCA is stupid, there's no two ways about it. But don't get excited about U.S. law being applied to Russians in their homeland, because it's not.
Re:move to development non US (Score:3, Insightful)
why oh why do people host their projects in the US ? ... what are the problems with this approach ?
Simply locating the project elsewhere isn't enough; for it to be beyond the reach of the US government, it couldn't be supported by the US at all including its citizens. As a US citizen I can be held accountable for whatever I do regardless of where the project is located. Even if I could work in a project in a foreign country without breaking any laws, I could still be sued by an American company if they didn't like the project I had worked on.
So you do indeed have a situation where US laws can restrict a lot of software development. These laws may seem unfair but they also prevent Microsoft from moving to the Cayman islands when the US threatens to break them up.
That's Intellectual Property for you... (Score:2)
Gates, Ballmer, Mundie and a host of other IT Leeches.
® Microsoft Corporation, 2001
Re:That's Intellectual Property for you... (Score:2)
Of course. What the heck are patents good for, if you can't use them to cut off the competition's air supply?
OK, so what patent is it? (Score:5, Informative)
(I fully suspect they do have a whole file cabinet full of patents, but I'd like to see them before I start making assumptions about the future of open source.)
Not only do we not know the specifics of the alleged patent, but we don't know if it's trivial or not. There's no guarantee it won't flunk the prior art or novelty tests.
The future of free software is assured by this (Score:2)
The worst: MS uses some crummy patent and gets DMCA import restrictions on all future SAMBA so that it could not be legaly used by any US company or any other DMCA slave state companies.
Enough BS like this from MS will make people think if Word documents are worth the price paid.
Re:OK, so what patent is it? (Score:5, Informative)
Re:OK, so what patent is it? (Score:5, Interesting)
AFAIK, you can't patent software in Australia, where Samba is developped. So, even if there were such a (US) patent, it would not stop Samba.
Once the Samba Team did the work and built a port of the new protocol, they would never be able to visit the US, or they would be arrested by the Microsoft Division of the FBI.
Would it be illegal to use in the US (Score:2)
Re:Would it be illegal to use in the US (Score:2)
patents control use. yes, it would be illegal to use the infringing product without a patent license.
however, patents aren't a matter of criminal law, unlike copyright. you can't be arrested for infringing a patent. you can only be sued. most likely, the patentholder would get an injunction against you using the patented process. theoretically, the holder could also get damages. they'd only bother with that if you were a big organization that they could suck a lot of money out of.
violating the injunction could land you in jail, for contempt of court. however, you still wouldn't get a criminal record and would normally be let out when the judge decided you were going to comply with the injunction. on the other hand, there's no limit to contempt of court: the judge can keep you there forever. so it's generally a good idea to obey injunctions. :)
Re:OK, so what patent is it? (Score:3, Informative)
So now instead of you being able to thumb your nose at the BSA because you use Open Source, they'll be gunning for your Samba installation.
Re:OK, so what patent is it? (Score:2)
> I assume that "high Microsoft official" was
> probably yanking Allison's (and indirectly,
> slashdot's) chain.
Nope. Definately not. Also it was 2 years ago, not 2 months, but journalism isn't an exact science
Jeremy Allison,
Samba Team.
Backfire (Score:2, Interesting)
I've read that when Microsoft has guys that help customers deploy Microsoft solutions, they use Samba if they need to integrate with a Unix network.
If Samba didn't exist, Microsoft would have lost the sale to that customer, because they'd have to either go whole-hog with Microsoft, or nothing at all. Chances are, most would stick with nothing unless their Unix boxes were too old.
Also, alot of non-Microsoft systems out there will be using Samba to server files to the Microsoft workstations. If the version of Windows after XP (Blackcomb?) didn't support SMB, I doubt the IT department would want to roll it out right away.
Not to mention that Microsoft would be forcefully obsoleting their own user base. Thats not something they are known to do willfully, witness the sufferings of people dealing with Win9x.
If Microsoft tried to do this, I expect that it would be a slow and gradual process, similar to the phasing out of WINS in favor of DNS with Windows 2000.
They just don't get it.... (Score:4, Informative)
Why don't they realise that they only reason the Internet has been so successfull is because it works by using a set of standard protocols that anyone can adopt and use. The best thing about the Internet is that I can run Linux on all my office machines and still access the Windows based services that others provide. By taking this road MS are in danger of marginalising themselves and not Linux. There simply has to be interoperability between different platforms in the modern business world.
In my company, for example, all of the tech guys use UNIX and all of the admin and sales use Windows. We have to interact with each other. If MS aren't going to allow it through their tools, it just means companies like mine will have to migrate to non-MS solutions for even the Windows machines. I just feel that MS are shooting themselves in the foot by taking this sort of approach.
Re:They just don't get it.... (Score:2)
Umm...successful at what? Certainly no one is making the gobs of money MS is used to.
Really what economic reason can be given for them to change their behavior? Because if there is a valid one, and not just "Microsoft should play nice because its the right thing to do", they will change their tune in a heartbeat.
Lets also not forget, Samba was always about working around Microsoft networking - coding around their API's. They are all public, so there is no reason they can't do so again. Patent or no patent, it is legal to perform reverse engineering to ensure compatibility.
Re:They just don't get it.... (Score:2)
Yes indeed, the buying decisions usually are made by admin and even some by sales. That's why things do fuck up so much. Just a couple weeks ago I was helping some guy try to work around a major buying mistake (to the tune of half a million dollars) the accounting people made by buying a bunch of computers with the wrong specifications. That's why techies need to break out of their shells (figuratively) and start cluing the bosses in on what actually works to save the company money.
Re:They just don't get it.... (Score:2)
sick of this. (Score:3, Troll)
I'm so tired of MS and thier contrary ways. they forever claim that they work for teh benifit of the consumer. Samba is the best if not only solution for interconnectivity between MS networking protocols and Unix. I've used this over and over again in MS, Apple networks, where there is a single Unix server. but yet MS intends to cut this off. how is this helping the consumer. True capitalism you dont muscle a customer to buy your product by stamping out the compitition you make a better product. Ms however does not understand this. Yet on the other hand we have the Gov getting in bed with big business. I really wish slashdot and the like activist woudl start writing their congress man or woman about this. when the old folks prescription goes up or someone threatens to take away there driving privaliges look how quickly they act. we need to adopt the same stance and start fighting for our rights as consumers in a free market.
Re:sick of this. (Score:3, Insightful)
From Micorsoft's perspective, the "best interconnectivity" is "no interconnectivity".
Re:sick of this. (Score:2)
Sorry; I should have quoted the original poster's "between MS networking protocols and UNIX". For that particular kind of interconnectivity, "none" is what MS likes best.
Terrible Article (Score:4, Interesting)
From reading the article I understand that there is the potential for Samba or any other open source app that realies on CIFS to have to mimic a function that happens when a user changes their password (I am asuming that this is part of MS/CHAP). The problem being that MS might hold a patent on something, that possibly would have to be implimented by said open source app and as a result MS could charge some sort of licencing fee. Maybe
What a friggin joke! The author comes up with a scenario which is has no factual basis, decides it could be a bad thing and then get various people in the community to provide quotes that agree with him.
This is FUD, a pure and perfect example of FUD. ZDnet is getting worse evey year.
Patents + Microsoft = Slashdot MegaThread (Score:3, Interesting)
As with all large companies Microsoft files lots of ridiculous patents. They do it for the same reason mine does, so that if they are sued by another company thay have something for swapsies.
It would probably not be a good thing for Microsoft if their customers could not attach Linux file systems easily. SAMBA is simply collateral damage in the high stakes game between EMC and Microsoft. EMC servers are very expensive and Microsoft would love to play bigger on that turf.
The bigger problem is that in the crackpot US PTO scheme you never know if a patent has been applied for on something until the government awards a 20 year monopoly in practicing it. The rules have been improved, i.e. made less open to corrupt abuse but they are still an extortionists charter.
I can't remember the last time Microsoft was the plaintif in a Patent lawsuit. They have been the victim of many Patent Trolls.
It would be an idiotic strategy for Microsoft to try to use patents to make .NET proprietary. But then again the tax cut for the ultra-rich and breaking the ABM treaty to build a 21st century Maginot line are crackpot ideas.
turn it around then... (Score:5, Insightful)
Re:turn it around then... (Score:5, Interesting)
That's why Microsoft's "Services for UNIX" product must have a kernel component - Win32 locking is unbearably primitive compared to POSIX locking. We can emulate Win32 locking semantics on top of POSIX, but it's not possible to do this the other way around.
Regards,
Jeremy Allison,
Samba Team.
Sure will be interesting to see them try... (Score:3, Insightful)
Lock-in (Score:4, Funny)
Re:If there's a patent... (Score:2)
Possible, yes (Score:2)
Re:Possible, yes (Score:2)
Except that this only applies to the US. Maybe sometime soon software licences will contain "Not for export to the USA" terms...
Re:Possible, yes (Score:2)
Re:Possible, yes (Score:2)
There's not even a"redirector writers kit" you can buy ! Microsoft doesn't *want* people to be able to write replacement redirectors. If you could do that, you might reduce dependencies on Windows Domain/ADS servers - why, you might even plug in your own authentication client, removing the need for a PDC/ADS server ! That would never do, now would it. Where would the monopoly go then ?
That's why almost no one writes decent replacement redirectors for Microsoft clients except Microsoft.
Why do you think all the PC/NFS products don't work very well ? Why do you think anyone who has to support Windows clients in a serious way (for a NAS product etc.) has to implement SMB ? It isn't because it's a beautiful or elegent protocol
Jeremy Allison,
Samba Team.
My bad (Score:2)
Re:No 3rd Party? (Score:2)
Having a Samba file system driver means that all of a sudden you have to update every last one of your client machines. Not only that, but you probably have to watch out for Microsoft breaking your driver with a Windows Update. Microsoft isn't particularly likely to break their driver, on the other hand, so you are safe as long as your file servers mimic a Windows server.
SMB is a horrific kludge of a filesystem, and the Samba developers will all happily acknowledge that. If you want to install file system drivers you would probably be better off using some other network file system. The beauty of SMB, however, is that every single Microsoft OS ever has a built in client. Leveraging that built in client saves adminstrators time and money.
Re:No 3rd Party? (Score:2)
I'll give ya every version of Windows, though.
Re:Isn't this what 'tridge' wanted? (Score:2)
But I understand. People over here think we're both Australian for some reason
Jeremy Allison,
Samba Team.
Re:Next you'll say MS is getting rid of TCP/IP (Score:2)
and since you think you were joking about MS replacing TCP/IP, read someone else's thoughts on the subject: http://www.pbs.org/cringely/pulpit/pulpit20010802. html [pbs.org]
Re:Next you'll say MS is getting rid of TCP/IP (Score:4, Funny)
Huh, didn't think of that one, right?
Re:Next you'll say MS is getting rid of TCP/IP (Score:2)
Re:Yawn. Why not a GPL'd NFS driver for windows. (Score:3, Interesting)
> windows 9x machines for USER level sharing.
Finally fixed in Samba 2.2.1a. I'm sure you'll now upgrade...
Jeremy Allison,
Samba Team.
Re:Double Edged Sword? (Score:2, Insightful)
Re:Double Edged Sword? (Score:2)
If M$ make more and more incompatible, then they'll end up making them not work with all the stuff that's out there (I know people, home users, who're still happy using DOS or Win 3.x because they simply don't need more).
At the moment, all this 'old' install base works quite happily, so they carry on adding to the figures that MS is compliant with.
Now, should MS break legacy compliancy, they'll irritate a lot of people who now can't communicate with the legacy MS installations, who need to look elsewhere (as they often loathe buying a whole new PC just so they can view the latest MS word files).
The whole point of MS keeping market share is to make things just compliant enough that old MS tech works, while making nudges that the new software is worth the cost of an upgrade.
Breaking the compliancy will remove a lot of legacy systems which will likely move to open source solutions/other compliant commercial systems, eroding MS Market share.
Rather than that hitting MS badly, they'll just improve legacy support in patches, making sure that all the open source stuff works with the latest MS.
Legacy is the whole reason we have the x86 architecture around still today.. And it'll be the reason that things still carry on working (to an extent) with MS into the future.
Malk
Re:Me Lose Monopoly? Uh-oh! (Score:2)
Re:But Of course (Score:2)
Unless they, oh... released a driver for NT and 2K.
Re:someone please (Score:5, Informative)
CIFS = Common Internet File System, also known as a slightly updated version of SMB, also known as the Windows file-sharing protocol. There is nothing really Common or Internet about it. (Did Microsoft give it this name?)
SAMBA = the SAMBA project, a free implementation of an SMB file server for non-Microsoft systems. SAMBA also includes directory services and other Windows NT Server features, so you could theoretically replace a WinNT box with an old Pentium running Linux.
By adding proprietary and patented encryption into the next version of the SMB protocol, SAMBA will no longer be able to emulate a Windows NT file server. At best, Microsoft clients would warn the user that they are not using a 'secure' connection, scaring management and IT support into buying a new Microsoft server. At worst, it could mean that Windosw XP cannot connect to SAMBA servers at all, forcing people to switch to Microsoft servers.
This is another effort by Microsoft to lock you into using their products. You will no longer be able to choose the type of server you want to run, if you want Windows XP compatibility.
There are two possible hopes:
1) Microsoft doesn't make this encryption a requirement to connect
2) Someone writes a SMB-compliant network driver for Windows XP
SMB will live. Must stay compatible with 9x/3.x (Score:2, Informative)
Re:That's an utter crock of shit! (Score:2, Informative)
Why not an open source solution? (Score:4, Interesting)
Re:Why not an open source solution? (Score:4, Informative)
There is a set of extensions to HTTP designed for precisely this kind of file sharing.
The protocol is called WebDAV [webdav.org].
WebDAV, a set of extensions to HTTP provide the following additional things that are especially useful for file-sharing: locking, versioning, logging, access-control lists, and searching (yes, with different grammars, too), and it runs over HTTPS along with HTTP.
Most people don't realize it, but A TON of products [webdav.org]((by such luminaries as Adobe, Macromedia, and Microsoft) support WebDAV (which is an extension of HTTP).
It was mentioned in the Halloween Document [webdav.org] as a decommoditizing protocol.
Furthermore, there are plenty of open-source implementations of webDAV on both the client- and server-side including:
mod_dav [webdav.org] (an apache module that makes it into a DAV-enabled server)
and
davfs [sourceforge.net] (a module for linux that makes dav folders seem like normal directories) Check it all out! -Michael p.s. By the way, it runs over HTTPS as well as HTTP, so don't get scared. p.p.s. In the interests of full-disclosure, I work for Xythos Software [xythos.com] and we make a robust, scalable WebDAV-enabled server.
Re:What does this mean for non-Microsoft users? (Score:3, Insightful)
Which means MOSX 10.1 will not be able to use the password encryption procedures without MS permission. This could be DCMA test if the SAMBA team decides to go ahead with the implementation of the password encryption. Of course, a black box shouldn't be patentable... I mean, if the code produces the right output with a different algorithm, then it should be kosher, (or parve, I'm bad with analogies).
Andrew