Samba 2.06 Released
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.
← Back to Stories (view on slashdot.org)
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
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?
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Tell your friends about xenu.net
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$. /samba or you have 'directories' that represent workgroups and in that directories that represent computers etc.
So in
that's what I would really like.
---
ftp://www.rtsg.com/pub
Lando
/* TODO: Spawn child process, interest child in technology, have child write a new sig */
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?
...Steve
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'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?
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.
--
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.
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?
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!
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.
.dot directory schemes, or whatever. As long as it worked (read: worked with NT/IIS/FP).
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
Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
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).
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.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
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)
--- polarbear
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)
I like music
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.
:) 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.
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.
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?
At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
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....
--
Time is on my side
So when will we see a package for Debian 2.1?
___
If you think big enough, you'll never have to do it.
Woo hoo. smbmount will finally work with the kernel automounter.
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.
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
-- I can't say enough in 120 chars!
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
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".
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. 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:
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.