I have been waiting a long time for Samba 3.0 becoming something more “concrete”.
IMHO This *could* be a milestone in the Linux vs. Windows debacle.
Add some nice management interfaces, polish the code so you won’t have to tweak Windows registry keys, like you needed with Samba 2.x + Windows XP, etc. and you might get some closer to a killer app…
I would consider a killer app to be something that you could not do with Windows (or another OS). This seems to be a way to make Linux do something that Windows already does.
This might be a nice incentive to switch if you have some other reason(s) for doing so (and I know that a lot of people do), but probably wouldn’t be the primary reasons – just like using Crossover to run MS Office on Linux. Unless I had some other reason that I wanted to make the jump, who cares if I can run MS apps in Linux, when I can already run them in Windows.
However, these kind of things are definitely needed to maintain compatability with Windows while at the same time reaping the benefits of Linux.
What is the main purpose of Samba? To share files with windows machines. And for just that simple task, the Samba Team have had to do all kinds of detective work for so many years. That’s the sort of nonsense you would never get with open standards. Hiding a file sharing protocol inside a proprietary jail is really silly, and if Microsoft was the original inventor, even protocols like POP, SMTP, TCP and HTTP would be completely proprietary. You never would be able to send email or communicate with others unless you paid something to Microsoft. Microsoft is a leech and a bad corporate citizen, especially considering that even itis quite happy to use and benefit from other open protocols
Darius, it’d be helpful if you visited the Samba homepage to find out what Samba really does before posting a comment. Or, read linux_baby’s definition of what Samba is.
Im curious what Windows administrators will think of samba 3.0 (please enlighten us, no trolling plz). My experience to windows administation is rather limited, because my personal preference goed to Linux. But they have Active Directory support, support for migrating to Samba, lots more. It seems rather interesting and promising from my point of few. I hope it will bring more competition to this ‘open’ market.
Samba has been better than Windows file sharing for a long time. we need to stop whining here people and start showing people how it’s better. You guys are sounding like Victicrats. “Windows is beating us booo hooo hooo. They’re cheating. The Government’s racist.” I use linux because I like it more. And I like Samba better than Windows File sharing (try adding a share in text only mode or through ssh). Nobody’s holding linux back except for LInux users. It’s up to us.
AAAAH. You guys are driving me nuts. I’m sounding like Rush.
i don’t know where you heard you need registry hacks to get xp to play with samba, or if it was the case at one time, but as it is right now, I can connect to my file server (samba) just fine from my XP box (my network is mostly linux, with one XP box).
I even previously had a Win2k Domain controller that samba used for an account db. Both my DC, and my XP workstation had no troubles connecting to samba without registry keys..
I’ll agree that GNOME/KDE need some sort of (<right click>–>Sharing) equivilent whether it uses samba or some other file sharing service.
I think that it would be more productive and fast to develop a free Nis+ and NFS client/server for Win32…
I already used Samba and it is impressive, but M$ “standards” are a mobile target. Why not make Win32 boxes “talk” to Unix machines using true standards like Nis+/NFS ?
I never saw anyone using a multiplatform distributed filesystem like Coda. Is it ready for production ?
Well, as an NT admin and old unix admin and nowadays working more on linux I must say that you can implement a lotta things with the samba projects and get real good results. Expertise is a must, also a Windows 2k or nt course might help you out since debugging is very often.
On the AD side of the story, I´ve played with samba-tng + openldap to get sth more of a AD flavor in a real world enviroment. Results were quite impressives, all you gotta have is time and dedication. Unfortunately both projects lack of a main front-end administration tool, I must recommend Directory Administration tool from a group of guys from Ecuador, it just kick a$$es in creating and editing users and groups.
I think the confusion with the registry hack was the one to disable encrypted passwords. Samba has supported this for quite a while. I don’t remember which version, but I think at least as far back as 1999. In 2002, there were people who didn’t know that Samba supported encrypted passwords and you didn’t need to hack the Windows registry to disable encrypted passwords.
I am pretty sure that Samba 2.x will be around for a while. I have been using Samba 2.2.8a on my FreeBSD 5.1 box as of late and it “just works”. I see no reason to upgrade to Samba 3.x unless there will be a major perfomance increase or some great new features previously unavaible…
Are there any benchmarks that compare Samba 3.x vs 2.x on Linux and FreeBSD ?
All of these == major progress for the open source movement.”
Good progress but plenty still to do.
The big weakness seems to me to be in accounts and general financial software, if Linux is going to compete on the office desktop. Another stronghold of Windows is in CAD – Linux has no equivalent of AutoCAD for professional work.
What are you talking about registry hacks? I have never had to touch the registry to connect to samba. I have a share with public write access (limited to local addresses) and a share with access only through my user account. Both are accessibly on both windows 98 and xp, simply by typing in the address and password if needed.
well, if you have no need for Active Directory. Then you should stick with Samba 2.x cos the major changes in Samba 3.x is mostly Active Directory related stuff.
“Another stronghold of Windows is in CAD – Linux has no equivalent of AutoCAD for professional work.”
For professional work, Parametric Technologies Corporation which is one of the three big corporate MCAD providers has their latest Pro/ENGINEER release ‘Wildfire’ built on Linux. HP has a certified workstation. It has been available since the end of last year. Remember that HP thought that they would release their own linux distribution in lieu of a RedHat distribution. HP is certified on RedHat 7.3 .
I have been waiting a long time for Samba 3.0 becoming something more “concrete”.
IMHO This *could* be a milestone in the Linux vs. Windows debacle.
Add some nice management interfaces, polish the code so you won’t have to tweak Windows registry keys, like you needed with Samba 2.x + Windows XP, etc. and you might get some closer to a killer app…
I’ll wait and see.
Great!
I would consider a killer app to be something that you could not do with Windows (or another OS). This seems to be a way to make Linux do something that Windows already does.
This might be a nice incentive to switch if you have some other reason(s) for doing so (and I know that a lot of people do), but probably wouldn’t be the primary reasons – just like using Crossover to run MS Office on Linux. Unless I had some other reason that I wanted to make the jump, who cares if I can run MS apps in Linux, when I can already run them in Windows.
However, these kind of things are definitely needed to maintain compatability with Windows while at the same time reaping the benefits of Linux.
What is the main purpose of Samba? To share files with windows machines. And for just that simple task, the Samba Team have had to do all kinds of detective work for so many years. That’s the sort of nonsense you would never get with open standards. Hiding a file sharing protocol inside a proprietary jail is really silly, and if Microsoft was the original inventor, even protocols like POP, SMTP, TCP and HTTP would be completely proprietary. You never would be able to send email or communicate with others unless you paid something to Microsoft. Microsoft is a leech and a bad corporate citizen, especially considering that even itis quite happy to use and benefit from other open protocols
Amen
Trolling so soon are we?
http://images.ucomics.com/comics/ch/1992/ch920808.gif
Darius, it’d be helpful if you visited the Samba homepage to find out what Samba really does before posting a comment. Or, read linux_baby’s definition of what Samba is.
some large orgaisations use Samba instead of windows servers as its more stable and scales up to the number of clients they use.
Im curious what Windows administrators will think of samba 3.0 (please enlighten us, no trolling plz). My experience to windows administation is rather limited, because my personal preference goed to Linux. But they have Active Directory support, support for migrating to Samba, lots more. It seems rather interesting and promising from my point of few. I hope it will bring more competition to this ‘open’ market.
i cant wait to play with the AD support and see what i can get it to do.
should be interesting
same comments as above
Samba has been better than Windows file sharing for a long time. we need to stop whining here people and start showing people how it’s better. You guys are sounding like Victicrats. “Windows is beating us booo hooo hooo. They’re cheating. The Government’s racist.” I use linux because I like it more. And I like Samba better than Windows File sharing (try adding a share in text only mode or through ssh). Nobody’s holding linux back except for LInux users. It’s up to us.
AAAAH. You guys are driving me nuts. I’m sounding like Rush.
serge,
i don’t know where you heard you need registry hacks to get xp to play with samba, or if it was the case at one time, but as it is right now, I can connect to my file server (samba) just fine from my XP box (my network is mostly linux, with one XP box).
I even previously had a Win2k Domain controller that samba used for an account db. Both my DC, and my XP workstation had no troubles connecting to samba without registry keys..
I’ll agree that GNOME/KDE need some sort of (<right click>–>Sharing) equivilent whether it uses samba or some other file sharing service.
-sp
Not sure about Gnome, but KDE does have a right click – share option I believe.
Let’s see…
Gnome 2.4
OpenOffice 1.1
Samba 3.0
All of these == major progress for the open ource movement.
I think that it would be more productive and fast to develop a free Nis+ and NFS client/server for Win32…
I already used Samba and it is impressive, but M$ “standards” are a mobile target. Why not make Win32 boxes “talk” to Unix machines using true standards like Nis+/NFS ?
I never saw anyone using a multiplatform distributed filesystem like Coda. Is it ready for production ?
Well, as an NT admin and old unix admin and nowadays working more on linux I must say that you can implement a lotta things with the samba projects and get real good results. Expertise is a must, also a Windows 2k or nt course might help you out since debugging is very often.
On the AD side of the story, I´ve played with samba-tng + openldap to get sth more of a AD flavor in a real world enviroment. Results were quite impressives, all you gotta have is time and dedication. Unfortunately both projects lack of a main front-end administration tool, I must recommend Directory Administration tool from a group of guys from Ecuador, it just kick a$$es in creating and editing users and groups.
Keep it clear and real!
yes! winxp needs registry hacks (depending how you have setup your samba configuration).
this are the keys/values you need to change:
REGEDIT4
[HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesNetlogonParameters]
“requirestrongkey”=dword:00000000
“requiresignorseal”=dword:00000000
[HKEY_LOCAL_MACHINESYSTEMControlSet002ServicesNetlogonParameters]
“requirestrongkey”=dword:00000000
“requiresignorseal”=dword:00000000
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNetlogonParamet ers]
“requirestrongkey”=dword:00000000
“requiresignorseal”=dword:00000000
cheers
SteveB
I think the confusion with the registry hack was the one to disable encrypted passwords. Samba has supported this for quite a while. I don’t remember which version, but I think at least as far back as 1999. In 2002, there were people who didn’t know that Samba supported encrypted passwords and you didn’t need to hack the Windows registry to disable encrypted passwords.
I am pretty sure that Samba 2.x will be around for a while. I have been using Samba 2.2.8a on my FreeBSD 5.1 box as of late and it “just works”. I see no reason to upgrade to Samba 3.x unless there will be a major perfomance increase or some great new features previously unavaible…
Are there any benchmarks that compare Samba 3.x vs 2.x on Linux and FreeBSD ?
The talk about registry keys relates to windows XP clients talking to a Samba server not Linux clients.
Been a while, but heres what I recall…
In the windows 95 days – password transmitted cleartext (ignoring updates)
In the windows 98/nt/+ days – password transmitted murkytext.
Samba in windows 95 days – default to cleartext password.
Samba in windows 98/nt/+ – default to murkytext password
If you need registry key stuff arounds then either update your clients, or your samba install… something is old.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fi…
“Gnome 2.4
OpenOffice 1.1
Samba 3.0
All of these == major progress for the open source movement.”
Good progress but plenty still to do.
The big weakness seems to me to be in accounts and general financial software, if Linux is going to compete on the office desktop. Another stronghold of Windows is in CAD – Linux has no equivalent of AutoCAD for professional work.
Yes sphantom, serge is right, you need to tweak around Windows XP registry base to be able to connect it to a Samba 2.2 server …
This is because of the “security” included with windows XP, that prevents it from uploading/downloading its desktop from the PDC.
What are you talking about registry hacks? I have never had to touch the registry to connect to samba. I have a share with public write access (limited to local addresses) and a share with access only through my user account. Both are accessibly on both windows 98 and xp, simply by typing in the address and password if needed.
Samba 2.2.8a and Gentoo
well, if you have no need for Active Directory. Then you should stick with Samba 2.x cos the major changes in Samba 3.x is mostly Active Directory related stuff.
“Another stronghold of Windows is in CAD – Linux has no equivalent of AutoCAD for professional work.”
For professional work, Parametric Technologies Corporation which is one of the three big corporate MCAD providers has their latest Pro/ENGINEER release ‘Wildfire’ built on Linux. HP has a certified workstation. It has been available since the end of last year. Remember that HP thought that they would release their own linux distribution in lieu of a RedHat distribution. HP is certified on RedHat 7.3 .
http://ptc.com/partners/hardware/current/hp.htm