Forgot your password?
typodupeerror
Windows Operating Systems Software Books Media Book Reviews Technology

Implementing CIFS 199

Posted by timothy
from the not-a-disease dept.
Bombcar writes "Anyone who has used Microsoft products in the last ten years has used the SMB protocol (now known as CIFS). Some have become experts in the usage of Windows file sharing, Samba, and more. We know that there can be a 15 minute delay before new machines appear in 'Network Neighborhood'. We've read the Official Samba 3 book, and follow the Samba mailing list once in a while, perhaps even answering questions. But there is a limit to the knowledge given by these sources." Read on for Bombcar's review of Implementing CIFS from Prentice Hall.
Implementing CIFS
author Christopher R. Hertel
pages 642
publisher Prentice Hall
rating 8 of 10
reviewer Tom Dickson
ISBN 013047116X
summary In-depth (but not too deep) coverage of the CIFS/SMB protocol

It is one thing to be able to use Samba, Windows, and the Common Internet File System (CIFS) protocol. It is another thing entirely to understand CIFS with sufficient depth to begin coding using it. This is where Christopher Hertel's Implementing CIFS begins.

This thick book (over 600 pages) begins with a history of NetBIOS in the DOS era. It quickly progresses to NetBIOS over TCP/IP (which evolved into the current CIFS protocol). Hertel documents the beginnings of quirks that will last throughout the life of the protocol. There is an RFC that was proposed in 1987, but many vendors have added extensions to this. (It might surprise you to learn that Samba has added extensions, which are covered in Chapter 24).

After the basic overview, he quickly dives into real coding of an actual (though simple) implementation. This will be his style for the rest of the book (except for humorous asides now and then). An aspect of the protocol, such as Name Resolution, will be explained in some detail, and then expounded in actual code (and in a few cases pseudocode).

The detail is good but not overwhelming. Some people (with names like Jerry Carter or Andrew Tridgell) will want more depth than this book provides, but for with a protocol as varied as CIFS, choices have to be made. As the Samba website mentions, this book is written in "Geekish." The book covers aspects of older and newer SMB/CIFS implementations, including a description of the NTLM2 challenge/auth system.

One thing that should be noted is that the code examples work, but as the author points out, they usually have little or no error handling. This is common to many books, but it is something to remember.

Now, should you get this book? If you're just a user, you probably don't need it. But if you've ever wished you could understand the Samba technical mailing list, or wanted to know why it takes up to 15 minutes to see a new machine, then you'll enjoy this book. If you want to utilize CIFS in any manner (even if just implementing Samba for clients), I'd highly recommend reading this. It will help you to understand what is going on on your network, even if you're not writing the code yourself. And if you want to be a Samba coder, it is required reading.

What didn't I like? I first read the book in an airport, and found that it relies heavily on having access to a computer. I would have preferred more explanations of code fragments than was given. However, this is a minor issue; most people who are implementing CIFS will be using a computer! I was also left with a desire for more information, but the large Appendix D along with many sources recommended provide for further study.

As a bonus, Appendix A tells you how to make a good cup of Earl Grey tea! That alone to some would be worth the price of admission.


You can purchase Implementing CIFS from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

This discussion has been archived. No new comments can be posted.

Implementing CIFS

Comments Filter:
  • by bbsguru (586178) on Tuesday March 09, 2004 @04:12PM (#8512877) Homepage Journal
    I know this is a difficult topic, but...Can't we just let CIFS to die, already?Alright, barring that, this really is a useful book. I wish I hadn't already learned it in the usual too-much-caffeine-for-rational-thought method.
    • by smharr4 (709389)

      It's all very well saying 'let it die', but just what would you replace it with?

      • by azzy (86427) on Tuesday March 09, 2004 @04:31PM (#8513072) Journal
        Easy, with the Posh Internet File System
      • by Kethinov (636034) on Tuesday March 09, 2004 @04:42PM (#8513192) Homepage Journal
        Replace it with nfs unix file sharing maybe? Oh I forgot. We're talking about Windows here. God forbid Microsoft should support nfs. It's not as if it's better than smb or anything and it's not as if Mac and the rest of the Unix world already support it </sarcasm>
        • by Anonymous Coward
          NFS is cool so long as you don't need passwords or authentication on your network resources. For other people that might be a little issue.
          • by caluml (551744)
            I hate NFS. You have to have the same user ID on all boxes, and have the same group IDs on all the boxes. Pfffft. Far too much trouble. Samba - well, if you log in to Samba as foobar, then your smbd process runs as foobar, and hence has all the right IDs and group memberships that foobar has on the box running smbd. Samba has got tonnes of options. Bah. NFS? Do away with it, I say
        • by Laur (673497) on Tuesday March 09, 2004 @05:01PM (#8513438)
          Replace it with nfs unix file sharing maybe? Oh I forgot. We're talking about Windows here. God forbid Microsoft should support nfs.

          Download Windows Services for UNIX [microsoft.com] for free from Microsoft, it contains a NFS client and server. I use this on my home network, no more Samba and its confusing config file (even with SWAT it is a nightmare). You can even choose to just install the nfs services and continue to use Cygwin for the rest of your Unix-on-Windows goodness.

          • by emil (695) on Tuesday March 09, 2004 @05:44PM (#8514041) Homepage

            There will be bugs in the M$ nfs server code. Will Windows Update patch them?

            The patch against SQL Slammer had been out for six months before Slammer took down South Korea and invaded a nuclear power plant. I don't want to install anything that requires special patching procedures.

          • My problem with NFS is that it requires all machines on the network to have the same userID->userName mapping. With CIFS, even under Linux, everything is dynamic. I can take my Linux notebook between my company's linux based network and my homes linux based network, and everything just works.
          • no more Samba and its confusing config file (even with SWAT it is a nightmare).

            While I certainly agree that setting up the advanced features of Samba (Samba as Domain controller) can be a little hairy for the uninitiated, if you're doing a simple implementation it isn't hard at all assuming you understand the concept of files shares in Windows and how to abstract it using text instead of the little hand.

            In fact, samba was the first application I installed and configured on Linux and I am just as happy wi

            • You seem a bit contradictory, you say "if you're doing a simple implementation it isn't hard at all" and then you say you had to consult a forum for help. ;) Don't get me wrong, Samba is a great piece of software, but easy it ain't. Have you ever used NFS? A single line in my /etc/exports file, run "/etc/init.d/nfs-kernel-server start" (on Debian) and I've exported my home directory to my LAN! (You should also put a few lines in hosts.allow and hosts.deny for security). I didn't have any problems setti
        • Replace it with nfs unix file sharing maybe? Oh I forgot. We're talking about Windows here. God forbid Microsoft should support nfs. It's not as if it's better than smb or anything and it's not as if Mac and the rest of the Unix world already support it

          Wrongo! Just like Win2k (which finally met OS/2's standards from 1994), Win2k and WinXP are now modern OS's supporting NFS with the free Unix Services for Windows Addon [microsoft.com] (which of course is appropriately titled 'Windows Services for Unix')

        • by cscx (541332)
          NFS is the caveman of network file systems. Sorry, we've moved a bit beyond that, it's not 1994 anymore.

          Linus Torvalds himself said "Linux's NFS 'sucks rocks.'"

          It's not as if it's better than smb or anything

          Wow, you're right on the money!
        • Replace it with nfs unix file sharing maybe?

          NFS isn't even good for Unix file sharing. Why would anyone want to use it on Windows?

          NFS is popular on Unix for exactly one reason: Sun gave it away for free, whereas AT&T wanted money for RFS (which, unlike NFS, actually supported Unix file system semantics).

        • by strobert (79836)
          uh, actually Microsoft does support NFS, both client and server. see their services for unix. I think this is the correct URL:

          http://www.microsoft.com/windows/sfu

          It has sounded very promising. Still on the look into list (I am actually more going to be using the auth sharing features to have our unix boxes publish password changes to AD).

          I will say I'm not the biggest NFS fan -- mainly becuase of portmap (for some of the reasons, see Steven TCP/IP Illustrated Vol I comments in the dicussion on NFS) --
      • This is an excellent question. How about Web Services Dynamic Discovery? Sure, it's vaporware at this point and it was proposed by the Beast. OTOH it has a good chance to be an open standard and it isn't limited to file and print sharing.
      • Appletalk would be a step up... Oh wait, Apple let that die. I'm only still using it at the office for 4 printers; LW 16/600s Will Not Die (especially for labels) and the Splashes are EFI products and consequently suck.
    • No, because 95% of the computers on the planet use CIFS.
      • by smharr4 (709389) on Tuesday March 09, 2004 @04:34PM (#8513102)

        Exactly the point I was trying to make above.

        As much as the slashdot crowd would probably hate to admit that Microsoft got something right, SMB/CIFS is the 'killer app' for sharing files and printers over a LAN.

        If there's another application that does the same job as SMB/CIFS and is:

        • Free
        • easy to use client
        • easy to configure server
        • multiplatform - Windows, OS X, varying strains of Unix, and linux
        then bring it on. Until then, we're stuck with CIFS.
        • Personally I think the an open protocol for this needs to be developed. I am the biggest MS supporter and also believe in closed source software, but I do believe in open protocols. The fact that the most heavily used LAN protocol is proprietary and requires reverse engineering is quite silly to me.
          • by MCZapf (218870)
            NFSv4 [nfsv4.org] looks promising to me. Of coure, that's what I thought two years ago as well. In any case, the goal for NFSv4 seems to be to take the best of NFS and AFS (and probably some other systems) and combine them.
    • what to replace it with for quick and dirty peer-to-peer. Not trying to troll, I genuinely don't know any alternatives. NFS isn't exactly easy to set up, and not much use when I go over to a friend's house to share files. Maybe FTP, but what if I want to share a printer? Plus you're still configuring an ftp server (I haven't done it yet, but it looks harder than adding a share to my smb.conf).
    • by El (94934) on Tuesday March 09, 2004 @04:25PM (#8513004)
      Can't we just let CIFS to die, already? As long as people are still running Windows and Windows is still using CIFS, it will be necessary to support CIFS for Windows interoperability. No argument from me that it is a horrible protocol for file sharing; but then NFS isn't much better.
  • by mauriatm (531406) on Tuesday March 09, 2004 @04:12PM (#8512879) Homepage
    Maybe a bit offtopic, but on my network I notice that Windows machines in the Network Neighborhood are slower to access than samba shares on linux machines. Go figure.
    • In my mixed platform (PC Mac, and more) network with PCMacLAN loaded, and Appletalk turned on for the PCs, I have found accessing a share and copying files to be far faster using that ancient protocol, even from Windows to Windows.
    • someone else did it, just check it out : samba faster [google.com]
    • by Anonymous Coward
      Maybe a bit offtopic, but on my network I notice that Windows machines in the Network Neighborhood are slower to access than samba shares on linux machines.

      Considering that the Windows machines are running upwards of 50 instances of netsky.d, this just shows the robustness of Windows Compared to Linux (which can't even run netsky.a)

    • MOD PARENT UP!

      I notice that, too. Also, Windows XP machines newly added to a Windows 98 peer-to-peer network have trouble seeing the Win 98 machines. Posting to official Microsoft newsgroups provides no answers to this quirky behavior. Of course, that may be because Chang, Li, Wu, Zhang and others have been told not to discuss it.

      I put some of the fixes for quirkiness together so that I could ask Microsoft if there was anything I am missing: Possible Solutions to Slow Network Browsing or Inability t [hevanet.com]
      • by Anonymous Coward on Tuesday March 09, 2004 @04:55PM (#8513348)
        One thing that should be added to that document is that all the Win9x machines should have the ability to be a Master Browser disabled (so long as there's at least 1 NT machine on the net).

        Otherwise, eventually one of the 9x machines with think it's won the browse election even when that should be impossible. This screws the network neighborhood. Very longstanding bug going back to WfW. You can check the state of your network using the "browstat" tool that comes with the resource kit.

        (Also, yer correct that NetBIOS or IPX will be faster than NBT for whatever reason. Make sure to adjust the "binding order" so that these protocols come ahead of TCP/IP. Can't recall exactly how to do this, sorry.)

        This might not be realistic for a home net, but install WINS/DHCP if possible and put the clients into p-mode. (no NetBIOS broadcasts)
  • O'Reilly Safari (Score:5, Informative)

    by Erik_ (183203) * on Tuesday March 09, 2004 @04:14PM (#8512904)
    And best of all it's available on O'Reilly's Safari [oreilly.com] service.
  • Network Neighborhood (Score:4, Interesting)

    by frenetic3 (166950) * <houston AT alum DOT mit DOT edu> on Tuesday March 09, 2004 @04:16PM (#8512921) Homepage Journal
    I've always wondered why on some machines it takes so damn long to browse the network on everything from 95 to XP -- most of the time I simply whimper and mumble incoherently waiting for it to eventually finish, but have never been able to diagnose the problem. Over the 'net it's even more agonizingly slow -- minute-long delays when pings are 30ms or less.

    The post suggests that this book tells the answer, but do any enlightened here know some typical causes of the ridiculously poor performance?

    -fren
    • by Bombcar (16057) <racbmob@@@bombcar...com> on Tuesday March 09, 2004 @04:22PM (#8512969) Homepage Journal
      The usual cause is badly synced browse lists.

      If you add a samba server and tell it to run WINS (with wins=yes), and then tell EVERY windows machine that the wins server is at (IP address of Samba Server), things usually speed up considerably.

      Also, there is (I believe), a C:\winnt\system32\drivers\etc\lmhosts file that works as a hosts file for WINS).
      • I thought WINS was outdated. Am I wrong? (Assuming a domain master and not an ad-hoc Win9x network.)
        • Win2K only supports WINS in some 'compatability mode', don't know if XP supports it at all.

          WINS is dying.
          • by droid_rage (535157) on Tuesday March 09, 2004 @04:59PM (#8513409) Journal
            Not true. 2k and XP both fully support WINS. It's generally configured in the DHCP scope, but it can be explicitly defined on the client.
            MS is trying to kill it off, but since 9x and NT boxes don't understand DNS for anything but internet name resolution, its demise is still a long way off.
          • by Anonymous Coward
            Its hardly dying, in fact WINS is still very much alive and well in many Win2k networks. Those who don't use it get to enjoy wondering why nobody can see anything in network neighborhood and can lots of problems. That whole "WINS is dead" crap went out the window a few months after Windows 2000 came out.

            With 2k/2003 MS took a HUGE step back in networking. In a technical sense AD in better in every single way. But in terms of ditching old things like WINS its a total failure. Back in the old days networking
            • by Bombcar (16057)
              In fact, that's why many times a Samba server added to the mix can help things. The samba server can act as an intermediary between the Win2k machines configured to speak DNS only, and the 98 machines that are howling for WINS information.

              WINS is only really dead in an all Win2k enviroment, and then only if you turn it off.
    • You're doing ~WHAT~ over the net?
  • ...but is there any reason why a CIFS client (or server) couldn't be written in a higher level language like Ruby [ruby-lang.org]?

    Obviously there'd be a speed hit, but it seems like it'd be a lot faster to develop in, and time-critical bits could be written in C and accessed via Ruby/DL [ttsky.net] or whatever.

    Ditto for Python, of course... same sort of advantages/issues.
    • by 110010001000 (697113) on Tuesday March 09, 2004 @04:27PM (#8513022) Homepage Journal
      For what purpose? Ruby is an esoteric language that hardly anyone uses and less people will use as the years goes on. This means that the code base will be unmaintainable.

      Now Java or C# is a real option. Microsofts next implementation will be written in C# as a matter of fact.
      • > For what purpose?

        Oh, the usual scripting language reasons: easier to program, easier to debug, reduces dangers of stack smashing and suchlike... all that.

        > Ruby is an esoteric language that
        > hardly anyone uses and less people will
        > use as the years goes on

        Ruby is a general purpose language that lots of people use and it will continue to grow in popularity.

        There, now we've both made assertions. So where do we go from here?
        • Well my assertions are based in fact. Do a poll of every software developer or programmer you know and ask them if they have ever written or seen a program written in Ruby. Then ask them if they have seen or written one five years (or three years) ago.

          The same principles apply to Eiffel, et al.
    • It seems to me that the bottleneck will be the network, not the application code. What's an extra fraction of a ms making a call in a high level language instead of C when the round trip time on the wire could one or two orders of magnitude longer?
    • Why not use a very high level language that has performance as good as C? OCaml is one such language (see my OCaml page [donkin.org] for links including benchmarks). OCaml is a functional language with good OO features and system API access, and would easily be capable of performing well for a CIFS implementation - no need to drop down into C for performance.

      Personally, I prefer programming in Perl - partly due to familiarity and the amazing CPAN (truly creates a very high level language where the primitives are thi

  • My Take (Score:5, Interesting)

    by 110010001000 (697113) on Tuesday March 09, 2004 @04:23PM (#8512985) Homepage Journal

    This book is simply the best reference available for CIFS. I only say that because I have spent $$$ getting everything on the subject I can. With the recent changes in Microsoft licensing every sensible IT professional should be exploring alternatives. A SAMBA server is a great alternative. This book is all you need to go from knowing next to nothing to knowing enough to impress your geeky Network Admin friends.

    This book is well written, clear and expansive. I didn't read it cover to cover (not at first anyway) I found pieces I needed, applied it, digested it, reviewed it and then went on to the next morsel I needed. If I missed something it was easy to find. By the way, it works with Win2K and WinXP neither of which is well documented by anyone anywhere.
  • by Anonymous Coward on Tuesday March 09, 2004 @04:23PM (#8512988)
    The full text of the book is available online as well; I don't want to slashdot the site, but google for "implementing cifs".
  • MacOSX Samba (Score:3, Interesting)

    by selderrr (523988) on Tuesday March 09, 2004 @04:25PM (#8513003) Journal
    what never ceases to amaze me is that my 400Mhz iMac can pull files faster from my AMD 1800xp than my P4@3GHz can...

    Both PCs run XP pro, the iMac runs panther. Go figure.

    As far as those 15 minutes concern, I got one solution for ya : rende-vous/zeroconf. Since iTunes/win can find macs using this protocol, a win port is allready done, so we can only hope MS sees the light and uses it for network scanning one day.
    • Re:MacOSX Samba (Score:4, Informative)

      by tupps (43964) on Tuesday March 09, 2004 @05:52PM (#8514171) Homepage
      Actually Apple gives away (BSD Style license) a code sample for implementing rendevous services. That should mean that anyone can/should implement rendevous if they need network discovery.
    • I've noticed the same thing in linux when pulling/pushing files between win2k workstations and a linux machine. The workstations are 800MHz Durons - 1800Mhz AthlonXPs, and the samba (2.2)/linux (2.4) system is a Pentium 2 333MHz (!)

      When pulling/pushing (making requests) with a Win2k workstation: narry a problem. Works much better than a setup with windows windows interacting.

      When pulling/pushing (making requests) with the linux system on any of the workstations: quite often the Windows machine will choke
  • Code examples? (Score:3, Interesting)

    by gpinzone (531794) on Tuesday March 09, 2004 @04:25PM (#8513010) Homepage Journal
    Could someone please explain what kind of code examples the book covers? I thought the whole point of modern OSes was to "abstract" everything for the user, including the method of networking.
    • Re:Code examples? (Score:3, Informative)

      by Bombcar (16057)
      The examples are of internal CIFS functions. As I said, if you just want to use CIFS, you may not need this book. This is if you want to write code that directly plays on a network using the CIFS protocol.

      jCIFS is one example, Samba is another.

      One code example is getting a browse list from another networked machine.
      • Okay, but what kinds of programs would you need to write that require intimate knowledge of the protocol that handles your OS' particular flavor of network shares? What I'm looking is for practical uses that a developer would be interested in or are these just code examples to illustrate how it works under the hood simply for educational purposes?
        • I dunno, maybe a simple version of WinNuke that lets you pick targets from a LAN? :)

          But, yeah, if you don't know what you'd do with the information, it probably won't be very useful.

          But if you want to work on the Samba project, for example, it'll be very useful.
          • So in other words, hardly anyone.
            • Yup. Just like hardly anyone has any use for the Kernel source. But it can be useful as a reference. The smbfs and cifsfs projects, jCIFS, Samba, and maybe even Microsoft can benefit from it, but a standard developer would have use perhaps only as a cautionary tale. :)

              However, a Samba implementer can gain knowledge from it and begin to understand in more depth what the level 10 error logs are saying, which can help increase time-to-solve on new issues. That's where I place the value of this book. Helps a g
  • overgeneralisation (Score:2, Informative)

    by tverbeek (457094)
    Anyone who has used Microsoft products in the last ten years has used the SMB protocol (now known as CIFS)

    Except for the people whose Windows boxes weren't hooked up to a network, or who instead used Netware for file/print sharing, or whose only loaded network components were TCP/IP and the adapter device. And even though it's installed by default, that doesn't mean everybody who failed to deinstall it actually used it.

  • by Bruce Perens (3872) * <bruce@perens.com> on Tuesday March 09, 2004 @04:40PM (#8513172) Homepage Journal
    Like all books in Bruce Perens Open Source Series [phptr.com], this book is under an Open Source license.

    Thanks

    Bruce

    • Now here is a guy I can respect. One who believes in the Open Source spirit enough to actually make the content of a book available for free. Kudos to Bruce for not being a hypocrite like so many of the Open Source "community".

      It would be interesting to hear about how well the books sell after being made freely available on the net. My guess is not very well, but I am a fervent anti-open source guy. Please let us know.

      Thanks

      • by Bruce Perens (3872) * <bruce@perens.com> on Tuesday March 09, 2004 @04:59PM (#8513400) Homepage Journal
        Thanks. There are 10 books in the series now, all treated the same as this one - online source and PDF, Open Source license. As far as I can tell, all have at least broken even, and most have made money.

        But the fact is that technical book authors are generally writing for some other reason than to get direct income from the book. Most do it for the intangibles - promotion of their own careers or projects they support, etc.

        What I like about this series is that the books need never die, since anyone can edit and print them. They don't get into that state where the publisher sells a few hundred copies a year on order and doesn't revert the rights to the author for years. Authors hate that.

        But we are careful with timing. We make sure the "pipeline" between the publisher and bookstores is full before the electronic copy is available. So, clone publishers don't have much incentive, as the stores have already filled their orders.

        I have to admit that this would not work as well if people liked to curl up with e-books. If that day ever comes, we'll change the strategy, but the end product will still be Open Source books.

        If you are very anti-open-source, it's probably because you don't yet understand the ways that Open Source works well for business and business people. I have a paper on the economic basis of Open Source that I'm working on, that you will probably find of interest. It should be out in a week or two.

        Thanks

        Bruce

        • I am interested in your paper on the economics of OS. I am personally convinced that the economics of Open Source are damaging to the software industry and to the software developer. Perhaps your paper will give me insight into this. I hope it will be available via your website.
          • by Bruce Perens (3872) * <bruce@perens.com> on Tuesday March 09, 2004 @05:08PM (#8513567) Homepage Journal
            Yes, I will put it up on the web. I think I can show you that Open Source isn't damaging to individual software developers and is of benefit to business and the economy in general. But it is damaging to a Microsoft-style business. Home refrigerators were very damaging to the huge industry that harvested, stored, and transported ice.

            Thanks

            Bruce

          • As you go from company to company, if you are not using OS (and many companies are not to any great extent) you are writing the same stuff over and over. Sometimes you are even doing that at the same company, where many groups are writing identical code!!

            Now the business has to pay for all this extra coding, coding that anyone can do - then they discover outsourcing.

            Had you been building things the business needed on top of robust OS packages, there would be no need to outsource you as productivity would
            • That is illogical. Assuming the outsourced engineer is as competent and as productive as the inhouse engineer, outsourcing will always provide savings and you will be outsourced.

              Of course you have pointed out the biggest failing (from my perspective) of OSS economics: less code needs to be written since there is code out there available for zero cost. This means less engineers (inhouse or outsourced) are needed. Thats great for the corporations, but bad for you and I.
              • Here's a little devil's advocacy....

                Big Company X that used to have 50 engineers suddenly only needs 40 because of OSS, so they let 10 go. But Little Company Y wants to do a project they think will require 20 engineers, but can't afford to hire 20. Some OSS tool is discovered that will help with the project, making it feasible to do with only 15 engineers. So company Y, rather than bagging the project and hiring 0 engineers, hires 15. Net change for the "industry" is +5, and now Small Company Y is able to
              • Of course you have pointed out the biggest failing (from my perspective) of OSS economics: less code needs to be written since there is code out there available for zero cost. This means less engineers (inhouse or outsourced) are needed. Thats great for the corporations, but bad for you and I.

                I think you are totally missing the point. Even with some free software available, it will still be in companies' best interests to get the code they want, written right now, by paying someone to write it.

                The OP

              • Of course you have pointed out the biggest failing (from my perspective) of OSS economics: less code needs to be written since there is code out there available for zero cost. This means less engineers (inhouse or outsourced) are needed. Thats great for the corporations, but bad for you and I

                What you are failing to realize is that corporations have an almost infinite thirst for code to be produced. The constraint? There are only so many developers to go around, and people to help explain what the develo
        • Is there a timeline for the digital versions of "Rapid Application Development with Mozilla" and "C++ GUI Programming with Qt 3"? I noticed that neither has links for the digital downloads. Just curious if it's because those are new titles and it just hasn't happened yet. Not that it matters much, my copy of RAD with Mozilla should be delivered today and I can enjoy it on paper. I would just love to have a copy on my Zaurus instead of having to lug the paper copy around.
    • by Anonymous Coward
      ... but don't have time to answer the Slashdot interview questions from last July [slashdot.org]?
  • For a moment, I thought this title read "Bombcar's review of Implementing CIFS from Apprentice Hell.'
  • by superpulpsicle (533373) on Tuesday March 09, 2004 @04:45PM (#8513225)
    As good as Samba is... you know M$ is always hiding something about their network neighborhood protocol. It wouldn't surprise me if the code reads "If Samba wait 5 minutes"
    • by MacDaffy (28231) on Tuesday March 09, 2004 @06:11PM (#8514411)
      Don't be surprised; you're right! I was doing QA for a CIFS implementation when the engineer ran across a bug that he just couldn't corral. We checked the RFC. We checked the code. We checked installation. Couldn't pin anything down.

      He finally put a sniffer on the network and analyzed the traffic between a Windows server, a Windows workstation and a workstation running our implementation. Turns out that the RFC instructs implementers to NEVER place anything other than zero into a certain location (LONGINT). However, that field was almost always non-zero when it was passed between the two Windows machines.

      The engineer put the length of the data transfer in bytes into the field and it has worked ever since.

      That incident cemented my negative attitude toward Microsoft. They don't try to win by looking good; they try to win by making everyone else look bad--even if that includes themselves. If you're uncertain about something that Microsoft is doing, use that premise as a reference point and you can't go wrong.
  • by dslamguy (644218) on Tuesday March 09, 2004 @04:49PM (#8513259)
    I read this book on Chris's web site even before it was published (yes, I have bought a copy) and it was an invaluable guide for me as I wrote a CIFS implementation. The book is fairly easy to read, even though it is highly technical. What it does cover, it covers extremely well.

    However, I did need the sniffer method of reverse engineering for much of what the book did not cover. One complaint I had is that I needed more information on the higher level protocols such as LANMAN for handling printer queues and this information was either non-existent or schetchy in the book. Although the book is long, much of it is taken up by a CIFS document which you could download for free on the internet. So I do think that the description part of the book could be more extensive (Sorry Chris). Maybe in the next revision.

    You might ask why I was implementing CIFS from scratch? Its a valid question, since Samba would/should be anyone's implementation of choice. I did it because we are developing a printer which is not GPL (and unfortunately not based on Linux). We are not using any GPL code in it, and so this was really the only choice besides buying it from someone (but where's the fun in that). I am planning on releasing this code under a BSD license, but it's not ready for prime time yet and I need to get back to it (in a couple of months).

    So this was a really good book for CIFS implementors, but how many of those could there be?

  • Didn't Microsoft rename "Network Neighborhood" to "Computers Near Me" in XP. That kills me?
    Was "Network Neighborhood" too technical. Of course the computers might not be physically near you.
  • I can understand wanting to use Samba in networks with a bunch of Windows shares. And I realize that the MCSE certification process involved a form of lobotomization. But beyond it's Microsoft-ness, what advantage does CIFS have over NFS and other network filesystems?

    I've heard of Linux-only networks that used Samba, and for the life of my I can't figure out why.
    • by MarcQuadra (129430) * on Tuesday March 09, 2004 @05:41PM (#8513991)
      Alright, I can give a good reason. NFS does NOT authenticate, it blindly trusts UIDs.

      So when I log into my friend's machine with his password, I'd be able to access my files on my machine as long as our UID is the same. Big trouble.

      CIFS, on the other hand, has authentication, so I can put my SAMBA server on the wide-open internet and be somewhat sure that someone would need my password to get my files. Try that with NFS and you'd be owned (or fileless) in minutes.

      Granted, there ARE ways to lock NFS down, and there are good arguments that maybe the modern file server SHOULDN'T authenticate, it should rely on another layer to handle that, but until it's easy as pie to get a Kerberos/PAM/NFS system working (no small task today), I'll stick to CIFS.
      • Okay, let me put this another way. I have a home network server with 160Gigs of unused harddrive space. So I decide to do automated backups of the clients to it. If everything on the network is either Linux or FreeBSD, why should I use Samba instead of NFS v4, when everything is local behind a firewall?
        • In that case you SHOULD use NFS, because it's easier to set up, fast, native, and 'clean'. I use NFS internally for my Linux and OSX boxes, but I run Samba as well on the port that connects to the 'outside'.
  • by LenE (29922) on Tuesday March 09, 2004 @05:50PM (#8514147) Homepage
    I was hoping that 3.0 would have been renamed as CIFiliS.

    I mean, it would give the right impression about the Windows native file sharing protocol, and would be great for PHB's.

    PHB: "Did you get that Samba thingy working on the server?"

    IT Guy: "No, the server has CIFiliS"

    PHB: "Oh. I'm sorry. You should run one of those virus checker things."

    -- Len

No hardware designer should be allowed to produce any piece of hardware until three software guys have signed off for it. -- Andy Tanenbaum

Working...