Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Announcements

Samba Team Announces Samba 2.2.5 28

Posted by Hemos from the hey-now-get-yer-fileserver-on dept.
GTO-Crank writes "Here's the changlog with all the fixes, enhancments, and sorce code for the new release of Samba 2.2.5. Also worth taking a look is this tutorial called "Using an LDAP directory for Samba authentication", and this tutorial called "Using Samba as a primary domain controller"."
This discussion has been archived. No new comments can be posted.

Samba Team Announces Samba 2.2.5 More

Samba Team Announces Samba 2.2.5

Comments Filter:
  • This is just a minor update by the looks of the change log, nothing much there for Linux users.
    A few compile fixes etc.. for HP/SUN users (who probably account for the majority of samba relient peoples)

    Isn't freshmeat the place for this kinda anouncement , especially seeing as 2.2.5 was release 6 days ago!

  • Sync (Score:1, Offtopic)

    by MindStalker ( 22827 )
    Probably not the right place to ask. But does anyone know how to get XP folder sync working properly when using a samba server? Is it possible? (It somewhat works without any special conf, but it gives many errors)

  • IBM's article about using Samba as a Windows Primary Domain Controller is Slashdotted. Not a good advertisement for IBM or DB2, is it?

    To any IBM engineers who read this: I suggest you learn how to set up a high volume web server from the Slashdot people.

    • I don't work for IBM and don't have first hand experience with their services setting up web sites, but I suspect that they know how to set up a capable high traffic web site (didn't they do the Olympics a while back?)

      OTOH, if I'm correct, that leaves two other options:

      1. someone powerful is deliberately Slashdotting that article;
      2. a heck of a lot of people are genuinely ininterested in learning how to use Samba as a PDC.
      Take your pick:)
      • It's not that no one at IBM knows how to set up a high-volume site. IBM just has poor management. They don't realize that something like this reflects on them more than advertisements.

        A lot of people want to use Samba as a PDC. Now that we have Mozilla and Open Office and Samba DCs, there are only a few more steps to eliminating Microsoft products from business offices. I'm not against Microsoft, but they don't serve their customers very well.
        • If you're eliminating Microsoft products, why do you need samba? :)
          • If you're eliminating Microsoft products, why do you need samba? :)
            I know you were being funny, but I've asked the same question: Why use Samba to serve Linux files to Windows PCs? Why not use NFS on the Windows PCs to reach those Linux files? Apparantly that's not a good idea. It's even in the NFS HowTo [ibiblio.org]: "[the NFS How To] will also not cover PC-NFS, which is considered obsolete (users are encouraged to use Samba to share files with PC's)"

            I would really appreciate any pointers to an open (GPL, BSD, whatever) NFS client for Windows, as I'd much rather go that route. Google [google.com] searches [google.com] turn up "free" demos of commercial software; the only open client I can find is PC-NFS, which is depricated (although I may try it anyway).

            Can anyone please explain why NFS on Windows is such a "bad idea" -- or did Samba simply kill PC-NFS? Is it a better idea now, in the face of M$ patents threatening to kill Samba?

            • I think the orginal poster ment, if you are eliminating Microsoft products, why would you still have Windows PCs to share files from Samba?

              You could be doing, NFS/CODA between all your Linux workstations.
              • I think the orginal poster ment, if you are eliminating Microsoft products, why would you still have Windows PCs to share files from Samba?
                Because we're still eliminating Microsoft products, we haven't eliminated them yet.
                You could be doing, NFS/CODA between all your Linux workstations.
                Exactly! And I want the Windows PCs to use the same protocols as the rest of the network. I don't want to force the network to conform to the minority Windows clients, I want the Windows clients to conform to the network! You're making my case for me -- thanks.

            • I think you answered the question already. Other clients, such as NFS, are too immature on Windows. Maybe they gave up in the face of Samba. I'd guess Samba has an edge over anything else on Windows, because it requires very little special set-up on the client-side.
            • The practical answer to your question is that almost every NFS implementation for windows is slow, buggy, and expensive while SAMBA for most unixes is fast, stable, and free.

              On the technical side I would even offer the opinion that CIFS (SMB) is a better file sharing protocol than NFS. For one thing, it is MUCH easier to secure.

              Unfortunately, for all its ease of use NFS is a pretty crappy way to share files, even under unix. All those people who whine constantly about replacing the perfectly reasonable X server should really be complaining about replacing NFS.

              I have a feeling that all those whiners are single desktop users who never get the idea of network computing.
          • In the world of real business considerations, it is necessary to go slow. There are many requirements besides technical ones.
      • or

        3. The site works fine, but there is a bad hop somewhere between ibm and the original poster. I vote 3, since it works fine for me.

Slashdot Top Deals

If you steal from one author it's plagiarism; if you steal from many it's research. -- Wilson Mizner

Close