Samba, Microsoft cooperate on new set of SMB/CIFS docs?

Samba, Microsoft cooperate on new set of SMB/CIFS docs?

Summary: One Samba contributor is working with Microsoft on a new set of SMB/CIFS documentation.A recent post on the Samba team blog indicates that code contributor Chris Hertel and his Ubiqx consulting company are working with Microsoft on a new set of SMB/CIFS protocol documentation.

SHARE:
TOPICS: Microsoft
14

One Samba contributor is working with Microsoft on a new set of SMB/CIFS documentation.

A recent post on the Samba team blog indicates that code contributor Chris Hertel and his Ubiqx consulting company are working with Microsoft on a new set of SMB/CIFS protocol documentation.

Samba is a longstanding open source project that provides code to allow interoperability between Linux/Unix servers and Windows-based clients.

The protocols will be published as part of Microsoft's MCPP/WSPP set,  the blog said.

"This is the first Microsoft-sponsored SMB/CIFS documentation to be made available without restrictions since the 1997 IETF draft specifications," the Samba team blog said. "The first new document, [MS-CIFS], covers the SMB protocol as implemented in Windows NT. It is almost 500 pages at present, and is just entering the review and markup stage. It should be available in a few months."

Topic: Microsoft

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

14 comments
Log in or register to join the discussion
  • Sweet...

    Zoom Zoom!
    JoeMama_z
  • RE: Samba, Microsoft cooperate on new set of SMB/CIFS docs?

    I'd prefer that Microsoft do its own thing rather than work with SAMBA considering the actions of some members of that team.
    Loverock Davidson
    • I agree...

      because interoperability and competition is a bad thing for the market.

      Btw, what actions of what members?
      Viva la crank dodo
    • The problem is that Microsoft, themselves, do not know how SMB/CIFS works.

      The code is the only documentation, and it is a
      hairball. Then, you have applications written to
      the very specific way that CIFS works, even though
      it is not correct according to the documentation.
      DonnieBoy
      • This is why Chris has source code access...

        Also, this is why he is prohibited from creating
        any code for Samba until a year after he has lost
        source code access (although I don't think even
        his memory is that good :-).

        Jeremy.
        JeremyAllison
    • Ah, Loverock, you made me laugh...

      So tell me, what is the cheapest Windows Server operating system I can get for me other than Windows Home Server? I don't want Windows Home Server components on top of Windows Server 2003, as I'm an enthusiast and very techie.
      Grayson Peddie
    • Good thing you're also just a Microsoft contractor

      Loverock, probably not as highly paid as Chris
      :-). But shills don't get paid much, do they.

      Hard work too, hanging out here all day posting
      pro-Microsoft messages to any story (unless
      Loverock is a group of people posting under the
      same account, which I've suspected in the past
      :-). Maybe you should learn Samba - I'm sure you
      could get a better paying job than being a lowly
      cog in one of Microsoft's "Image management
      Teams" :-) :-).

      Jeremy.
      JeremyAllison
      • Thats just crazy...

        imagining a paid shill couldn't post anything more substantive than loverock. If he got paid, certainly he could afford to find (MS funded) studies to back up any of his claims.

        Viva la crank dodo
      • RE: Samba, Microsoft cooperate on new set of SMB/CIFS docs?

        The first new document, [MS-CIFS], covers the SMB protocol as implemented in Windows NT. It is almost 500 pages at present, and is just entering the review and markup stage. It should be available in a few months.<a href="http://ipadbagblog.com/"><font color="LightGrey"> k</font></a>
        zakkiromi
  • And, this points to the problem that MS does not even know how their own

    product works and can not write proper documentation!!

    Pretty funny.
    DonnieBoy
    • Not true, a little unfair.

      Documenting this stuff is code archaeology in many
      cases. Microsoft coders are working on code, so it
      makes sense to hire an outside contractor to do
      this work.

      Jeremy.
      JeremyAllison
      • But it does beg the question...

        How much of SMB etc did Microsoft ever (properly) document?

        I'm guessing you know, or know someone who does, what with the EC extravaganza over it all.
        zkiwi
        • Not enough of it :-).

          And there are still parts that need more work. See
          here:

          http://blogs.zdnet.com/BTL/?p=22078

          for details :-).

          Jeremy.
          JeremyAllison
  • Tread carefully ...

    MS has yet to show their sincerity in their recent overtures to the Linux community. The past has shown that they embraced, engulfed and finally extinguished competing software vendors (EEE).

    "If you can't beat them, join them." MS may not exactly be joining, more like putting their foot in.
    orionds