Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Unix Operating Systems Software

Samba 2.06 Released 102

LazLong wrote to let us know that Samba [?] 2.06 has been released. A whole slew of bug fixes, as well as some new features. The technical documentation is available, or just go all out and grab the tarball.
This discussion has been archived. No new comments can be posted.

Samba 2.06 Released

Comments Filter:
  • Now that there is an new version of Samba we should have those mindspring tests again. Wasn't a big part of that benchmark serving win98 clients through samba?
  • Also, the Samba page mentions that Using Samba from O'Reilly will be available for downloading.

    George
  • by jd ( 1658 ) <imipak@ y a hoo.com> on Thursday November 11, 1999 @07:39AM (#1541916) Homepage Journal
    I want my money back. Freshmeat listed this as being "low urgency". New features is -always- high urgency! Even if I never use them. Why do you think I've 4.5 gigabytes of Open Source software I've never even untarred?
  • by Xemu ( 50595 ) on Thursday November 11, 1999 @07:43AM (#1541917) Homepage
    There's a whole world of mirrors out there:
  • by BorgDrone ( 64343 ) on Thursday November 11, 1999 @07:47AM (#1541918) Homepage
    All we need now is a way to browse the samba network. I know there are app's like gnomba and LinNeighbourhood. but I want to be able to mount the 'network neighbourhood' under /samba and be able to browse that in every application just like you can allways access the network neighbourhood from any open / save dialog in window$.
    So in /samba or you have 'directories' that represent workgroups and in that directories that represent computers etc.
    that's what I would really like.
    ---
  • I think it was actually apache, i don't recall seeing anything about samba on there. the benchmarks were for NT and IIS vs linux and apache, IIRC.
    ^. .^
  • by DaveHowe ( 51510 ) on Thursday November 11, 1999 @07:48AM (#1541920)
    Now that there is an new version of Samba we should have those mindspring tests again. Wasn't a big part of that benchmark serving win98 clients through samba?
    Not entirely sure about that - they have fixed quite a few bugs, niggles and security issues, but I don't see much if anything that would make it faster. In any case, if the test showed that NT was still faster than Samba, it would be dismissed by the linux community as biased, due to NT being optimised for Win95 and not NT workstation, or just wrong. If it showed NT slower than Samba, then Microsoft would dismiss it for almost the same reasons :+)
    --
  • by Lando ( 9348 )
    ftp://www.rtsg.com/pub

    Lando
  • Samba is a fairly heavyweight player. The executable for smbd alone on SPARC is over 1MB in size. It would be nice to see a single task, multithreaded model. That would really kick ass IMHO.

    Or maybe not. I could be wrong. Comments?
  • The new mounting code for this should be available in this release. Still reading the changes...

    Once you mount a drive from another machine it's as simple as cd /mnt/'the old NT server'/

    Done..

  • by Hrunting ( 2191 ) on Thursday November 11, 1999 @07:55AM (#1541925) Homepage
    All the bug and code fixes aside, the entire reason that I'm downloading this release is for their updated documentation. When 2.05 came out, the Samba team came under heavy fire for not updating their documentation (the old smbmount pages were out of date even before that), especially considering they had completely redone the option system for smbmount and other utils. It looks like they've redone that again, but the documentation is now a) up-to-date and b) many times more verbose than it ever was.

    Kudos to the Samba team for listening to and executing the ideas of its users.
  • I didn't see any mention in the documentation, but does anyone know whether this will compile on MacOS X server? I tried this with Samba 2.0.4 right when OS X came out, and couldn't get it to work right, but I don't know whether it was something misconfigured or due to the changes I had to make to the config file to get it to compile.
  • Another very important one ... Large directorys now get listet much faster !

  • I know, but what I want is:

    smbmount // /samba
    cd /samba/MyWorkGroup/Server1/share1

    I dont want to mount every share, but I want to mount the whole network at once, and have it update dynamically as new servers/share's become available. just like the network neighbourhood works in windows.

    ---
  • I'm running a Linux Box as an NT domain controller for a small farm of Windows sheep. So far, the 95/98 people cannot use user-level sharing because when their machine tries to retrieve the user list for the domain from the Linux box, samba cannot provide. Has this been fixed?
  • Nod,
    Sorry misread your comments. Shouldn't be too hard to do though. Now that mount is working, ie no longer smbmount, I would think that it would be fairly easy. Just live nfs has virtual connections that kick off when they are used.

    Lando
  • I'm not sure whether this is the best forum to address this.. but I'm always alittle miffed about how the initial release of most software is in the form of a tarball. This is fine - I know how to use them. My problem is that alot of stuff under RH6 and other distros use RPM, or dpkg, or other such utilities. That makes life difficult for me, because then I need to uninstall the old package (making sure to backup the config files) and then install the tar. If I later get the packaged release (usually a few weeks later), then I gotta do that all over again! Man... it's times like these I wish linux was alittle more standardized for some things. Packaging should not be this difficult.

    --
  • it seems like this could be handled with a program on the main server that generates a script whenever a computer plugs in or logs out, and having clients run that script through crond or somesuch.
  • Im running Mandrake 6.0, based on Rh 6.0.

    When I got the RPM it didn't work properly, saying that it had an unresolved symbol in libreadline.

    I made myself an RPM from the SRPM and it works properly now.
  • ....the initial release of most software is in the form of a tarball. ... My problem is that alot of stuff under RH6 and other distros use RPM, or dpkg, or other such utilities. ... Packaging should not be this difficult.


    It is only difficult for the browsing-impaired unwashed masses. On the Samba website, you have the option of downloading both RedHat and Debian packages for the new samba release.

    They're on the Samba FTP site, too. Gee.

  • you can always untar the samba source, cd packaging/Redhat and then read README, you can then build the rpm for your computer and install the rpm. This worked very well on my machine
  • "The philosophy is laugh in the face of danger. Oops, wrong one. 'Do it yourself.' That's it." -linus
  • Sorry,
    Got a little excited. I've been waiting for this release. And just threw the file on one of my sites. I'll leave it up until the feeding frenzy is over.

    ftp://www.rtsg.com/pub/samba-2.0.6.tar.gz [rtsg.com]

    Lando

  • I haven't been able to my hands on this hot little item, but it occured to me that if the mount functionality has been changed, could one get these SMB shares to mount through 'automount'? I could never figure out how to get 'automount' to work with 'smbmount'.

    Does anyone have any ideas how to get this to work correctly?
  • that thought also crossed my mind by it not an option.
    I am connected to a samba network with more than 1500 computers which all contain a few shares.
    that would mean mounting thousands of shares.
    ---
  • I'm not sure whether this is the best forum to address this.. but I'm always alittle miffed about how the initial release of most software is in the form of a tarball. This is fine - I know how to use them. My problem is that alot of stuff under RH6 and other distros use RPM, or dpkg, or other such utilities. That makes life difficult for me, because then I need to uninstall the old package (making sure to backup the config files) and then install the tar.
    Hmm. RPMs are wonderful things - precompiled, ready-to-run executables in a container that allows the end-user to install it simply. Tarballs, by contrast, are just compressed blocks of source with a make script and are much harder to use
    That said, tarballs were around long before RPMS, and there are still some distros out there that can't support RPM - but there aren't any that can't do tarball, plus the commercial Unixen (like HP) use a different system again. It is much easier to do it ONCE as a tarball, than five or six different ways for five or six different systems.

    If I later get the packaged release (usually a few weeks later), then I gotta do that all over again! Man... it's times like these I wish linux was a little more standardized for some things. Packaging should not be this difficult.
    I suspect at some point RPM will become the default - but for the moment, tarball is easier for the writers (if not the users). But that said, why are you installing the RPM over the top? once you get the tarball up and running, it must be easier to leave it than to de-install and re-install just so to have the pretty packet version rather than the homespun.... although I agree it makes life easier in the long run if you upgrade with another RH CD.
    --

  • by Jeremy Allison - Sam ( 8157 ) on Thursday November 11, 1999 @08:37AM (#1541944) Homepage
    Shaman wrote :

    > It would be nice to see a single task,
    > multithreaded model. That would really kick ass
    > IMHO.

    Actually, no, I'm afraid it would suck :-). Come to one of my Samba talks if you want the gory details why, but essentially the problem is with threads switching user contexts. Think about how Samba provides UNIX security....

    Cheers,

    Jeremy Allison,
    Samba Team.
  • they have fixed quite a few bugs, niggles and security issues, but I don't see much if anything that would make it faster.

    As it should be. One of the reasons I like Open Source Software is that the programmers generally concentrate on real improvements, not arbitrary benchmarks.
  • If only L. Ron Hubbard were alive to see Xemu, doing good for mankind.
  • They have fixed quite a few bugs, niggles and security issues, but I don't see much if anything that would make it faster.
    As it should be. One of the reasons I like Open Source Software is that the programmers generally concentrate on real improvements, not arbitrary benchmarks.

    Hmm. I /semi/ agree with that one - Improving speed is as good an upgrade as improving functionality, provided you don't go for speed either
    1. Purely to match a benchmark that has no relationship to reality and
    2. that you don't sacrifice functionality, security or reliability just to eke out that extra half-milisec.
    even *I* could speed up Samba drastically - just take out all the checks for password and username, and give everyone full access to the entire tree :+)
    --
  • by Anonymous Coward

    Samba is Great!

    Daily we transfer many gigabytes of mission critical data to our unix systems using Samba.

    Two years and many terrabytes later we have not lost of single bit.

    We've experimented with alternatives, such as:

    FTP (fast, but users hate it)
    NFS clients on PCs (pain to setup and maintain plus $$$ per client)
    Syntax (worst of the bunch, pain to set up, pain to administer and expensive)

    but nothing matches samba for speed, ease of instalation, maintainability, stability and interoperability with Windows95 and NT.

    If Bill was really serious about hurting nix, he would import those hard coding Ausies and put them to work on windows 3000.

    Speaking of windows, how well does Samba work with Windows 2000 and all that silly active directory garbage????? Right now Samba barely does domains, and domains will be going the way of the dodo bird in a year or two.

    Instead of chasing proprietary MS interfaces such as PDC/BDC and active directory, perhaps "the comunity" should come up with an alternative, open directory service.

    Yikes, I'm rambling. Back on track:

    Three Cheers for Samba!

  • What would really be nice is some sort of way to fake RPM into thinking that the new tarball you just compiled and installed was something installed through RPM. Perhaps some sort of file list that comes with the tarball that could be sent to the rpm command. In other words, a way to tell rpm "I just installed this myself, here's what it looks like".

    It is really nice having a nice rpmized version installed because you don't have to remember things like what files make up the program.
  • Before you flame me, let me explain. The company I work for hosts Frontpage sites on NT (by necessity, not choice). We would like to use NAS for the NT Servers as we do for all the Unix servers, to increase relability and simplify backups. But Frontpage makes extensive use of ACLs which Samba either ignores entirely or does not support correctly. Mapping ACLs to unix bit permissions is, when you think of it, both highly limiting and kind of retarded. There is no way to cover NT ACL functionality with Unix bitmask permissions.

    I'd like to know when Samba will really support ACLs. I wouldn't care if it faked them using DBM files, if it used Solaris native ACLs, strange .dot directory schemes, or whatever. As long as it worked (read: worked with NT/IIS/FP).
  • I think everybody here is missing the point. When I turn on my Windows machine, I don't have to type in anything to get to my friend's computer over the Network Neighborhood. Even the guys with the BeOS boxes can get onto Network Neighborhood without having to type a whole bunch of cryptic crap and make ANY sort of directories, because with over 3000 computers on my network here at school, somebody would have to be insane to want to use Samba for this purpose. Why is it so hard to make Linux/Samba act EXACTLY like Network Neighborhood? Completely Hassle-Free.

  • Check out smbsh...it does just that...it creates a logical shell that allows you to access all of the "Network Neighborhood" in /smb. It's a bit buggy (pwd doesn't always work when in /smb) last time i checked, and it doesn't make teh computers available from any program, but it might help.
  • There were benchmarks done by PC Mag (I believe it was PC Mag) well after Mindcraft that not only did IIS vs Apache, but did Samba vs NT.
  • the new syntax is

    mount -t smbfs -o username=foo,password=bar //foo/test /data/test

    which seems to work better then the previous version... Though i do notice a delay now between when the comand completes and when the file system is actually mounted..

  • You can delete the .pwl files in the c:\windows directory; that usually forces you to log on the next time. And if you do enter a password when you do log in, it'll ask you every time (which usually isn't what you want).
  • I had this problem as well with Mandrake 6.1...

    I'm not exactly sure how to use SRPMS so I guess I'll wait for the Mandrake RPM...
  • No. See http://bstc.net/~brian/docs/ for a workaround
  • My biggest problem with Samba at the moment is I don't get notified when my password is about to expire on the network, so it often ends up getting expired since I tend to boot in to Windows less often than the expiration time (Around 6 months.) I'd be great if 1) Samba would warn me when my network password is about to expire and 2) let me change it so I don't have to boot into Windows at all.
  • Jeremy,

    Are you going to be in the New York/North-Eastern area anytime soon??? Would you like to talk at my college?

    Thanks,
    Steven Rostedt
  • It's news isn't it?

    Plus, it seems that Rob thinks it's cool, so it gets mentioned. That's how the site got started, and how it is run today.

    Live with it.
  • Worked fine here...

    Worked with Mandrake 6.1 with shipped kernel and custom kernel

    (and yes, the client is a win98 box)
  • I have a T1, need suggestions for it's use. E-mail me with suggestions

    Well let's see...

    Multiple Linux Distrobution mirror (like I'm doing with 4 PPC distros and a T3)

    Samba mirror

    Kernel.org mirror

    HOWTO site

    Public Quake server!!

    or

    mirror all of your favorite **Pron** sites!

  • This is how Slashdot has been run since I can remember. In fact, seems like the new release of software posting has been slowing down if anything over the last year, even as posting in general has gone way up. It has not increased under Andover. I'm actually surprised at how little has changed. (availability/speed aside)
  • Actually it can be pretty simple. Log in as root and run "rpm --rebuild package-1.2.3-4.src.rpm". It will untar the files (in /usr/src/$DISTRONAME/SOURCES) and compile (in /usr/src/$DISTRONAME/BUILD) them based on a script (in /usr/src/$DISTRONAME/SPECS). If the compile doesn't work right (like it doesn't use the Autoconf variables you want) just edit the spec file in ./SPECS and run "rpm -bb ./SPECS/packagename.spec" to build binary (bb) packages. Simple.
  • Now if we can just get Windows NT to do that:

    C:\>CD \\SERVER1\SHARE1
    '\\SERVER1\SHARE1' is an invalid current directory path. UNC paths are not supported.
    --
  • Alas, I was looking over the comments and thinking "Wow, finally the people moaning about software updates on Slashdot seem to have died off", only to find this post.

    Somebody made this complaint last time a software update was posted on Slashdot, and it bugged me. And lo and behold, somebody did it again, and it still bugs me. Here's the gist of what I told the last guy.

    Slashdot is News, so says the title.gif. :) Every now and then, perhaps once or twice every few weeks, one software update gets passed on to Slashdot. This is to be compared to the 118 items currently on freshmeat for the last three days alone.

    Coming from the other side, Freshmeat currently has exactly one post that isn't a software update that is also on Slashdot, the XMMS Plugin Contest.

    No matter how you look at it, that's a very small margin, one I think is forgivable by even the harshest critic. I mean, it's not like there are categorical criteria to Slashdot submissions. If we can talk about national-security threatening Furbys, then why can't we mention a new version of an ubercool software suite?

    Your options are simple. Continue reading Slashdot and cope with the occasional version update, continue reading Slashdot and scream in agony at the occasional version update, stop reading Slashdot, or download the source code and make your own site completely devoid of such daemon spawn.
  • I couldn't get 2.0.6 to work either from RPM or source under Mandrake 6.1. It broke things so I was forced to revert to 2.0.5a. It seemed to be an error w/ the readline library although I didn't investigate much. Anyone else have this problem or find a fix?
  • I was going to make an RPM (or try to) of it but since it didn't work for me I didn't bother. I'll have to wait til someone else makes one that will work and save teaching myself how to make RPM's for another project.
  • Simple? I'm sorry did you read your post?
    I'll tell you what is simple.
    ./configure; make; make install

    and if ./configure defaults aren't your bag, you do ./configure --help and see what options you have. You don't need RPM, and this applies to every distributed peice of software for the linux platform. I really see no use for RPM at all.
    (you should see how easy adding stuff is in freebsd)
  • Actually, no, I'm afraid it would suck :-). Come to one of my Samba talks if you want the gory details why, but essentially the problem is with threads switching user contexts. Think about how Samba provides UNIX security....

    I guess the solution to that would be to implement Samba as a kernel module. Then all of the routines that give you UNIX user security are available and well tested.

    Well, get on with it! ;-)

  • Not only that... but Samba is one of the few "mission critical" apps that affects LOTs of netizens/networks... (The others that qualify are Bind and Sendmail)... So.. it makes sense for it to also appear on Slashdot....
  • So when will we see a package for Debian 2.1?
  • The reason I tend to stick to RPM is that fact that it knows where to put the whole asortted array of files. Some distributions expect files in certain places for other program to locate correctly. Just untarring a new program keeps everything in one spot. I know many include a make install sub section and that works okay. The problems really arise in administering the system. Maybe I want to upgrade or delete a package...

    Having an RPM installed is easy to move around. If I would use a make install script I would have problems later tracking down all the files to either delete/change or update.

  • Woo hoo. smbmount will finally work with the kernel automounter.
  • I don't know if this is exactly what you had in mind, but you can use:

    rpm --tarbuild [tarball]

    to create a .rpm file from a tarball.

    Hope this helps.
  • Try the smbsh program:

    # make smbwrapper
    # cp bin/smbsh bin/smbwrapper.so /usr/local/samba/bin

    $ smbsh
    Username: spruce
    Password:
    $ ls /smb
    total 0
    0 ./
    0 ../
    0 ACCOUNTS/
    0 ACADEMY/
    0 ACOLYTE/

    Very cool.

  • HP and Northrop Grummond (sp?) have donated some code to help with this. Needs a little work though. I'm targeting 2.0.7 (2.0.6 oops bugs notwithstanding :-) for this.

    Jeremy Allison,
    Samba Team.
  • Remember, Samba is not Linux specific. It is usable on all major *nix platforms, which do not support RPMs.

    Tarball is the packaging format usable by anyone running a *nix platform.

  • I use a program called sharity to browse large networks (no smbmount on the IRIX, FreeBSD, SunOS and AIX machines I run). It basically creates a special mount at /CIFS where you can browse the network. It's not really mounting shares. It just redirects back to localhost where it (I'm assuming) talks with sharityd which browses the network at an application level.

    Unfortunately it costs a lot of money. Free student licenses are available however. I don't know if smbmount does this as I don't use linux.
    ----------
  • The smbwrapper subsystem code, smbsh, will not compile under glibc2.1. So Linux will have to wait.

    Compiling smbwrapper/smbw.c with -fpic
    smbwrapper/smbw.c:1429: warning: `struct stat64' declared inside parameter list
    smbwrapper/smbw.c:1429: warning: its scope is only this definition or declaration, which is probably not what you want.
    smbwrapper/smbw.c: In function `stat64_convert':
    smbwrapper/smbw.c:1431: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1432: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1433: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1434: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1435: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1436: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1437: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1438: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1439: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1440: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1441: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1442: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1443: dereferencing pointer to incomplete type
    smbwrapper/smbw.c: At top level:
    smbwrapper/smbw.c:1448: warning: `struct dirent64' declared inside parameter list
    smbwrapper/smbw.c: In function `dirent64_convert':
    smbwrapper/smbw.c:1450: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1451: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1452: dereferencing pointer to incomplete type
    smbwrapper/smbw.c:1453: dereferencing pointer to incomplete type
    make: *** [smbwrapper/smbw.po] Error 1
  • Because that ain't the Linux Way.

    C'mon boy, you've installed X, you can handle this.


    No, really, I think it would be easy to make a network neighbourhood type client that runs under Samba. It would have to be a separate system run by the server, but it is true, that mountin 1500 computers is not very wise. The client could check the server's dynamically updated list of computers, display them in a Windows sytle view (even with the cute computer icon!) and mount them when you want to access them.


    I ain't coding it because I know jack about unix programming, though, and I have a long time to go before I am competent to be doing projects like that.
  • even *I* could speed up Samba drastically - just take out all the checks for password and username, and give everyone full access to the entire tree :+)

    That wouldn't speed up samba drasticly, since that is not where the bottlenecks are. I imagine filename searching (case insensitive), name mangling, and oplocks are where the worse bottlenecks are.

    Password authentication is rarely ever a bottleneck
  • They're a coming--but not from Mindcraft.

    Steven, Senior Technology Editor, Sm@rt Reseller
  • Hmm. I /semi/ agree with that one - Improving speed is as good an upgrade as improving functionality, provided you don't go for speed either

    1.Purely to match a benchmark that has no relationship to reality and
    2.that you don't sacrifice functionality, security or reliability just to eke out that extra half-milisec.

    Note that a great many benchmarks are likely to come under catagory one. It's far easier to automate something which is unrealistic than something which does have some relationship with the way things are accessed by people.
  • Samba is a fairly heavyweight player. The executable for smbd alone on SPARC is over 1MB in size. It would be nice to see a single task, multithreaded model. That would really kick ass IMHO

    You are trying to apply NT biased issues about threads vs processes to unix. Where they do not apply. NT tends to use threads extensivly because process creation is very expensive under that OS.
    Also handling of multiple users gets even more complicated than it is already (It can be complicated now becuase of the MS client's ability to use a single TCP connection for multiple users.)
  • No. See http://bstc.net/~brian/docs/ for a workaround

    Note that this is only for registry wizards. Don't even think of showing this to the average end user :)
  • I'm not sure whether this is the best forum to address this.. but I'm always alittle miffed about how the initial release of most software is in the form of a tarball.

    That's becuase the tarball format is useable by the vast majority of people.

    My problem is that alot of stuff under RH6 and other distros use RPM, or dpkg, or other such utilities.

    Not everyone is using RH6 (or for that matter Linux). Even if they were maybe they want different settings from those Red Hat (or whoever) prefer.

    That makes life difficult for me, because then I need to uninstall the old package (making sure to backup the config files) and then install the tar. If I later get the packaged release (usually a few weeks later), then I gotta do that all over again!

    If you have the tarball what's stopping you building your own RPM? Also why do you need to install the program twice? (Especially when the publically available RPM is likely to have been compiled without CPU optimisation.)
  • Due to crypto export restrictions, the RPMs don't contain SSL support (you don't run SAMBA without SSL support, do you?).

    Unlikely in the case of an RPM put together by the Samba team and on the main FTP site. More likely becuase the SSL support is "experimental".
  • if ./configure defaults aren't your bag, you do ./configure --help and see what options you have. You don't need RPM, and this applies to every distributed peice of software for the linux platform. I really see no use for RPM at all.

    You probably want "./configure --help |less" in practice. This will work for any program supporting the GNU config program on various operating systems.
  • The header files that come with OSX server are seriously f**ked.

    F**ked in what way? Samba 2.0.6 compiles cleanly... the only issue is that MacOS X Server isn't recognized by the config.guess and the config.sub as distributed in Samba. That's easily remedied, especially by someone of your prowess by copying the ones that Apple supplies in /usr/libexec.

  • Why pay for a BSD clone when you could just run BSD?

    You could do some of your own research. See Apple's Mac OS X Server Product Page [apple.com]. Now, you might not want to run it, but you should be able to see why some other people might want to run it. Just in case, here are some keywords:

    • Apple File Sharing
    • Macintosh Manager
    • WebObjects
    • Cocoa OO Frameworks
    • Apple Hardware Support
    • Supported Quicktime Streaming
    • NetBoot Server for MacOS
    • ISV app support (especially in comparison to *BSD or Linux on PowerPC)
    • MacOS compatibility environment (w/o CPU emulation)

    These are all above and beyond the fact that it has a Mach kernel with BSD 4.4isms and for the most part plays nicely with other UNIX variants.

  • As soon as I do some more testing, I'll get a Mac OS X Server .pkg package up on next-ftp.peak.org [peak.org]. My Samba 2.0.4b [peak.org] and 2.0.5a [peak.org] packages are already up there, including instructions for compiling it yourself.

    Another place to look for software for Mac OS X Server is Stepwise's Softrak [stepwise.com] service.

    If you are in a hurry, the just copy the config.guess and the config.sub from /usr/libexec to replace the ones given in the Samba distribution. Configuring the smb.conf and other Samba issues are pretty much the same as other platforms.

  • Unfortunately, when I try to get automount to work with smb filesystems, I get the following error messages in /var/log/messages:

    Nov 12 11:23:02 helsinki automount[10387]: attempting to mount entry /lsi-ou-server/c
    Nov 12 11:23:02 helsinki automount[10392]: cannot find mount method for filesystem smbfs

    My automount line looks like this:

    c -rw,fstype=smbfs,user=administrator,password='dele ted' "//lsi-ou-server/c$"

    Thanks for your help and all the wonderful Samba work!
  • even *I* could speed up Samba drastically - just take out all the checks for password and username, and give everyone full access to the entire tree :+)
    That wouldn't speed up samba drasticly, since that is not where the bottlenecks are. I imagine filename searching (case insensitive), name mangling, and oplocks are where the worse bottlenecks are.
    Yes, I know - it was meant as a humourous statement, giving a patch everyone could see as being a *bad thing*. If I had any /good/ ideas to speed up Samba, I would either have tried them or suggested them (depending on if my coding was up to the trial)...... Password authentication is rarely ever a bottleneck
    --
  • even *I* could speed up Samba drastically - just take out all the checks for password and username, and give everyone full access to the entire tree :+)
    That wouldn't speed up samba drasticly, since that is not where the bottlenecks are. I imagine filename searching (case insensitive), name mangling, and oplocks are where the worse bottlenecks are.
    Yes, I know - it was meant as a humourous statement, giving a patch everyone could see as being a *bad thing*. If I had any /good/ ideas to speed up Samba, I would either have tried them or suggested them (depending on if my coding was up to the trial)...... Password authentication is rarely ever a bottleneck
    --
  • Have the best of both worlds, use setup.sh [mmedia.is] it builds and RPM out of almost any GNU Autoconf based tarball. That way you can keep track of what you have installed, and where it is.

Our OS who art in CPU, UNIX be thy name. Thy programs run, thy syscalls done, In kernel as it is in user!

Working...