Learn from Samba-Man Jeremy Allison 118
Jeremy is a leading Samba maintainer, and therefore one of the world's leading experts on Samba, which is often held up (along with Apache and the Gimp) as a sterling example of efficient and useful Open Source development. In the interest of full disclosure, we must mention that Jeremy is now employed by VA Linux, but that his primary responsibility is still Samba, just as it was when he worked for SGI. Look for Jeremy's answers to your questions within the next week.
"Point and Print" (Score:1)
Samba has done this since some point in the 1.9.x line, since I have a few systems that have been doing it for that long.
Look at PRINTER_DRIVER.TXT in the docs that come with the Samba source tree. It goes into all the gory details. You have to get your hands dirty and rip into the crap that companies like HP give you, but it DOES work. They say "add this printer" and it just pulls it down and starts going. HTH.
Oh, and with regards to your ACL / "out of Unix groups" dilemma - let me add a hearty AOLer style reply: me too! What you seek would be very useful.
What I'd need in order to trash our NT servers (Score:1)
I work for a US governement agency, and we use Samba extensively in our mixed Solaris/NT (soon to be Solaris, NT & Linux) network. In fact, partly because we are able to provide better support for our Solaris servers and partly because a lot of analytical processing is done under Solaris and Solaris can't straightforwardly mount NT filesystems, most of our users store most of their data -- even their NT-native data -- on the Samba servers, not the NT servers. We don't see a liklihood of this preferance going away anytime soon, and we would seriously like to do away with our NT servers if at all possible, and replace them with servers running either Solaris and/or Linux.
We are now in the process of redesigning our authtentication and name services schemes, and at least in my division -- what with the extensive use of Unix -- Active Directory is not a leading contender to provide any of these services. What we need is good support for NT desktop workstations (MS Word being a business requirement and all) and Unix file, print and computational servers. Preferably Unix and NT systems would obtain authentication from the same source, e.g. a Kerberos or LDAP server. Note that, as contrasted to some "appliance-like" implementations of Samba servers, we need to support login authentication to the Unix machines (both through telnet and xdm -- most users use eXceed on their NT workstations) as well as mapping SMB shares, so having Sabma be able to use an authentication service is not sufficient; xdm, telnetd and login must also be able to use the service. (We currently use Samba in security=server mode -- both the NIS master and the NT PDC are controled by the same adminstrative team and a single person will add userids to both -- so most authentication is handled by the PDC, except for Unix login and xdm which are handled by NIS.)
In addition to login authentication, we do of course need file services for the NT workstations. But full control of file ACLs from the NT client side is an absolute long-term requriement. Today, our users control file security by creating files first in Unix and setting the permissions, or by logging into a Unix server and doing a chmod/chgrp on the file after it gets created by Samba on behalf of the NT workstation. By setting restrictive default permissions in the Samba configuration, this is relatively safe, but it is a huge pain. Thus, in some cases where file sharing among several NT users must be supported and complex security requirements exist, users will typically create the files on the NT servers. On the Unix side, we have maybe 100 groups for a few hundred users, and have had problems with users being in more groups than are supported by the OS. Also, many groups completely change membership from month to month depending on project staffing. Thus, whatever our solution is must support very fine-grained and dynamic control over access control lists, and it must be straightforwardly controllable from the NT client side, preferably though Windows Explorer.
One other thing we make use of in NT is NT Server's ability to transparantly download printer drivers to NT workstations. Since our users don't have administrative access to their workstations, they are not able to install their own printer drivers. NT deals with this configuration by storing the appropriate driver as part of the printer share on the NT side. When a user maps an NT server-based printer to their workstation, the driver is automagically installed on the workstation. If Samba can't do something like this, it could cause a pretty big headache for us. (Samba may do this today, I'm not sure).
Finally, one major issue is how one goes about distributing software and patches to NT workstations, and also how they may be remotely controlled by help desk and/or administrative staff. Currently we us Microsoft's System Management Server for this, which kind of sucks in a lot of ways. Still, it would be utterly fabulous if it worked the way it seems to have been designed to, and it really does provide some essential services today. This is kind of pie-in-the-sky, but a solution that didn't address some of the function lost if SMS were shut down could easily result in whole lot of lost shoe leather.
There's probably some other things, but I've listed what I think are the big ones. If authentication and name services can be integrated for NT, Samba and Unix, if users can have fine-grained control over file ACLs, if printers can be transparently mapped without having to install drivers by hand, and if an alternative solution can be found for software distribution, remote control and other services provided by SMS, then I think we stand a chance of shutting our NT servers down completely. Partial solutions, such as addressing only the file ACLs and integrated authentication, are likely to help to get rid of a large number of the NT servers, but are not likely to eliminate our dependance on NT Server altogether.
Jeremy, any light you can shed on these issues would be greatly appreciated.
Thanks,
Samba Performance (Score:1)
Any insights into why the otherwise stellar performance of Samba is so miserable when using the MS-DOS Windows-networking client?
I use Norton Ghost to do a lot of system cloning, and when using the DOS client to save a hard drive image to a server, throughput to Samba maxes out at about 3MB/min (for reference, a null parallel cable does about 4MB/min). Throughput to an NT box on much lower end hardware goes about 80MB/min. It's usually faster to make the image on a real NT box (or even a VMWare fake NT box) and then FTP it to the Samba server.
I understand that the peculiarties of the client can have a large impact in the performance of SMB, but what does the MS-DOS client do so different that would account for a nearly 2 order of magnitude decrease in performance?
How about a role reversal? (Score:1)
I'm curious if you ever contemplated reversing Samba's role in connecting Windows clients to server-based print, file and authentication services.
Imagine, instead of building software that makes a *nix server behave as a Windows server, create software that enables clients to understand the behavior of a *nix server.
It occurs to me Linux could continue it's best of other-breed approach to functionality by presenting a combination of the best of Windows/SMB, UNIX/NFS and Netware services to a open-source windows client custom built to understand them.
What do you think?
Windows 2000 Publicity (Score:1)
Rusty.
Re:Samba Performance (with DOS) (Score:1)
Have you tried other DOS clients? (See my webpage).
Just for testing, have you tried downgrading Samba to a lower protocol, such as LANMAN2 or even CORE?
I wished I had more time to check out these kinds of things since clearly the Samba guys leave these things for other people to fix. And rightly so since they have no need theirselves. I guess we have to scratch our own itch, eh?
And yes, some people still have a need for DOS. Perhaps not in the US, but World != US.
Re:Replacing NT (Score:1)
(I actualy disagree with Pheros_7f4 about Microsoft changing things intentionally, but that's a side issue...)
The usual sense of "replacing my NT PDC" is to provide all PDC functionality in Samba in the much the same way that MS pioneered it, (a bit of a long-term task).
What's your opinion of providing the unix equivalent of an SMB server, with things like DFS supported on top of automounter tables, much like "homedir map" already does?
--daveThe Future of Samba (Score:1)
http://theotherside.com/dvd/ [theotherside.com]
Brain drain. (Score:1)
Other standards (Score:1)
Re:Did you get any VA Linux stock? (Score:1)
I'd consider them both to be hardware development companies. NetAttach [netattach.com], which VA Linux paid about $40 million in stock and cash for, "has developed Linux-based technology for creating a high-availability storage appliance," according to the press releases. (They're part of the Network-Attached Storage [NAS] market.)
TruSolutions [trusolutions.com] got about $200 million in cash in stock, and the main thing they bring to the show is their engineering abilities in designing "Linux-based high-density rackmount servers." This is the purchase that sounds a bit questionable to me -- I don't wanna knock 'em, 'cause I'm all for taking the money and running, but can you really take a look at their website and picture that as a company worth $200 million?
Cheers,
ZicoKnows@hotmail.com
SGI's feelings toward Linux (Score:1)
Hi, do you keep in touch with your former colleagues at SGI? I was just wondering if they harbored any bitterness because Linux basically destroyed their company. Does their morale suffer from their PR department making a much larger effort to associate the company with Linux than the effort they put into promoting SGI's own IRIX?
Cheers,
ZicoKnows@hotmail.com
SMB And routers (Score:1)
Windows remedies this situation by using a WINS server, which is a replacement for the broadcast nature of name resolution. Using a WINS server, each client (regardless of their subnet) can query the WINS server to resolve names and browser requests. These requests can (and will) be routed if several subnets exist.
Another way to deal with cross-subnet browsing is using NT's LMHOSTS file, and including both Domain Controllers in the file, but that's another story!
SAMBA (Score:1)
It's difficult to get teachers to depend on something other than a chalkboard... the flaky Windows server certainly wasn't helping their confidence in the file server idea. It took a major dive last week so I finally made the somewhat time-intensive transition to Linux/Samba.
I've never had a single problem with any of the servers I have running Samba on Linux (a couple have 250-300 day uptimes!). My only wish would be for Samba to be faster / more intuitive to configure without having to use a GUI or web interface.
Thanks again for your efforts,
--SONET
http://www.hbcsd.k12.ca.us/peterson/technology
Re:Samba File Locking (Score:1)
(Tony@ServaCorp.com) Intrspy/Cmdspy don't work under NT.
smbfs for other operating systems? (Score:1)
sharing files (Score:1)
Samba File Locking (Score:1)
Do you know what the cause of this incompatibility is, and is this something that will be fixed in the future?
Re:Samba File Locking (Score:1)
The app in question is using the Clipper/Codebase command set. (Don't ask why).
Feel free to email me (remove the ANTISPAM).
SP7 (Score:1)
Re:Challenges for new contributors (Score:1)
Has the Samba Project Received Static From MS? (Score:1)
Re:MAPI support in Samba? (Score:1)
The thing with MAPI is that it isn't a protocol per say, its MSRPC running over Netbios. You would need to decode the RPC calls. Not an insurmountable task, mind you, but not necessarily one that is necessary considering Exchange's web support and IMAP/POP3 support.
Share permissions? *shudder* (Score:1)
But then I realized that is just my personal opinion. I've always thought that as long as you have your permissions set properly in the first place, you don't need to restrict them again.
Never mind the fact that you aren't really talking about NT share permissions - you just want to implement them, and pretend you are implementing real ACLs.
It's still a bad idea.
Re:Share permissions? *shudder* (Score:1)
This is why, IMHO, Samba should not set up ACL emulation; let the OS/FS do that.
Pizza (Score:1)
Front Ends (Score:1)
Mike Roberto
- roberto@soul.apk.net
-- AOL IM: MicroBerto
Active Directory & SOAP (Score:1)
Finally, out of curiosity, since 2000 implements a few more "web-oriented" features in NTFS, will Samba be collaborating with (or stealing from) Apache to implement this level of functionality?
Re:ACLs - Here's what we use! (Score:1)
Works simply, with no need to mess around patching fsck and other fs programs.
Corp Backing (Score:1)
What are your thoughts on HP making money on samba?
How do you see development changing with a corporation having a vested interest?
Mod this up (Score:1)
Re:What do you think of my work? (Score:1)
BDC functionality? (Score:1)
Re:How about YOU get a life (Score:1)
Columbine is still a tragedy many are still recovering from. People got killed and a nation went into a pandemonium over it. Jon Katz should not of been dragged into the troll even though he tends to be over the top at times.
Re:SGI's feelings toward Linux (Score:1)
I don't think it was Linux that destroyed SGI.
A while ago, SGI's 3D abilities on their workstations were far superior than anything available for any other platform, and worth the price.
I believe that they failed to keep ahead of the advancing PC industry. Games like Quake provided the critical mass to make 3D accelerator cards a commodity, thus lowering the price of them, while SGI's prices remained high.
SGI did little to keep their 3D abilities state-of-the-art, so their high prices no longer seemed worthwhile and people began buying generic PC's to do their renderings instead of SGI.
(This is all IMHO... If anyone cares to fill me in with more information on the downfall of SGI, please do so.)
Re:NetBEUI (Score:1)
I would love to see NetBEUI support in Samba! Especially with the Procom NetBEUI stack for Linux [procom.com], announced recently.
It would be a great idea to support NetBEUI. That protocol may be dying, but it has two advantages for small networks that aren't present in TCP/IP:
Question though: Assuming the Linux NetBEUI patch is integrated into the kernel, would it be best to have the Linux kernel handle the NetBEUI setup (node discovery, defending conflicting names, etc.), or do it internally within Samba?
As NetBEUI is a low-level protocol like TCP/IP, there's an argument for doing it in the kernel (thus letting other programs use NetBEUI as well). But, much of the existing code is already in Samba, and there's also an argument for doing it in Samba (it would be fairly straightforward, just remove the TCP/IP wrapper the SMB packets get encapsulated in, and put them directly on the wire via NetBEUI).
(Just FYI for newcomers to this protocol: there's a difference between NetBIOS and NetBEUI. NetBEUI is a network protocol, like TCP/IP. NetBIOS is a programming interface, like sockets, that was designed and optimized for NetBEUI (much the same as the socket API was designed for TCP/IP).
Re:Samba Performance (Score:1)
Disclosure (Score:1)
Good work /. ... it may be full of chaos, rumour and reposts, but it's critical for independence that disclosure is maintained. It also protects your back from accusations of impropriety.
End of Days (Score:1)
Will Samba ever die?, if so, how?
question (Score:1)
Full PDC support and the Samba TNG Merge (Score:1)
Samba configuration (Score:1)
Cheers - Baz
PS thankyou for making my life so much easier (as a sysadmin for 300+ machines).
Re:Share permissions? *shudder* (Score:2)
...or some flavor of ACL stuff, e.g. the stuff that was being worked on as a POSIX draft [www.guug.de], or various implementations based on various POSIX drafts (Solaris and Digital UNIX both have POSIX-draft-like ACLs, and other UNIXes might as well - there's a project to implement them for Linux as well [bestbits.at]), or non-POSIX-style ACLs such as appear on HP-UX.
Re:Share permissions? *shudder* (Score:2)
But that's not necessarily what the poster to whom you're replying was asking for. He/she said:
Said tab is the tab for the file's ACL.
He/she then said:
If it ties in with the Linux patch in question, that'd obviously be per-file ACLs (it'd also be difficult, given that NT ACL semantics, which is what clients will be expecting, aren't the same as POSIX ACL semantics), and if it's done "in a file Samba maintains", it could, in theory, be done with per-file ACLs (I think some commercial SMB-server-for-UNIX does that), although the problem then is that said ACLs don't apply to UNIX users, just to SMB clients, so if somebody grants or denies Joe Blow access by adding an ACL entry, that doesn't necessarily mean that if Joe Blow logs into the box running Samba, or a UNIX box that's NFS-mounted stuff from the Samba box, he will necessarily be granted or denied access.
Re:Windows 2000 lack of support (Score:2)
No. SMB's file model is similar to NFS's file model - "please give me N bytes from the file starting at an offset of X" or "please write the following N bytes to the file starting at an offset of X". Typically, the server doesn't care what the bytes are, it just reads them or writes them.
Some SMB and NFS servers might offer an option to translate between different text file formats if the file is a text file, but I don't know whether any do.
I've read music and video files from our (Network Appliance's) SMB servers; I would expect it to work reading from a Samba server as well (there's no reason why it shouldn't work).
Re:SGI's feelings toward Linux (Score:2)
--
smbclient and OS/2 compatibility (Score:2)
Samba on Windows? (Score:2)
What about buffer overflows? (Score:2)
Given this, how do you respond to the argument that vendors only fix their problems when threatened with disclosure, and therefore when you find problems you should not merely notify, but also threaten to disclose the problem if it is not fixed?
Thanks,
Ben
Re:Samba as a security measure? (Score:2)
The SAMBA group has always maintained that their duty is only to replicate MicroSoft's protocols, not expand them.
> using the SMB protocol... instead of normal Unix file transfer protocols... that are better known
Ugh. Tell your PHBs that "Security through obscurity is no security". If they want security, use ssh and encrypt.
Samba TNG - What is it? (Score:2)
My understanding is that it intends to provide a fairly complete emulation of the RPC mechanisms in WinNT and 2000, so that Samba can properly emulate domain controllers. Of course, I could be all wrong here.
Would such a project assist in decoding and emulating the 'wire' protocols of MS applications such as MS Exchange or DCOM? Does it provide any services to native unix applications that don't already exist, or is the goal only to co-exist with Windows networks?
--
Samba's future (Score:2)
Extending SMB (Score:2)
Thanks so much for all your work. I'm sure you know how nice it is to be able to get rid of NT on as many boxes as possible.
My question is:
With linux slowly creeping in as a more ubiquitous platform, have you ever thought about adding open extenstions to SMB to enable new features?
Thanks,
Blue
Taking blame for broken-ness (Score:2)
How do you deal with stability issues on the NT side of samba? For instance, I have the smb client running on a lot of machines here, because I don't control the NT servers for some departments, and need access to their shares. I have to re-mount those boxes every hew hours, and I'm sure it's because the NT boxes are dropping/resetting my connections, but it looks like instability in the client end. Do you have to deal with that sort of issue a lot, and, if so, have you guys ever considered rewriting the SMB server subsystem.. for NT?
--
blue
Did you get any VA Linux stock? (Score:2)
And if so, have you been able to dump it yet, or are you forced to hold onto it for a certain matter of time? What's the feeling around the company about the stock having lost about 72% of its value (from 320 down to 90) in a little over three months, with no sign of bottoming out yet, all while as of last week, VA Linux was still shelling out dough to gobble up other companies like TruSolutions and NetAttach? Any panic in their eyes yet? How low do they think it'll go?
Cheers,
ZicoKnows@hotmail.com
haphazard development (Score:2)
However, as Samba (and the Samba team) has grown, the software has become more difficult to obtain and install. As a specific example; if I want/need TNG, I can't download a package from my linux distributor of choice and
Furthermore, HPUX users (who are essentially already burning in hell, because they have to use HPUX) often don't have a "real" C compiler, or CVS capabilities, so they can only get what somebody else ports - and there is no HPUX 11.00 precompile of TNG available from any reputable source that I know of.
So, the question is, will this trend continue, or will the Samba team make a real release on a more definite schedule than "real soon now"? The current code split makes planning difficult.
Also, does the ongoing rancor directed toward Win95/98 support found on Samba team mailing lists indicate that there will never be adequate support for these very popular desktops?
And finally, how do you feel about HP's shameful lack of attribution in their release of Samba for HPUX? I noticed that when Blackdown got dissed by Sun everyone was up in arms, but I never saw any beefs from the Slashreaders when HP announced CIFS support without crediting you guys.
Roblimo, I hope you won't filter any of these questions out... JA can hand hardball questions, I've seen him do it.
MS-Windows SMB defined? (Score:2)
Re:Replacing NT (Score:2)
Re:Samba as a security measure? (Score:2)
NT machines only support this via a 3rd party utility (sslproxy), Win9x machines need a proxy server running sslproxy because they cannot handle it directly at all.
Re:sharing files (Score:2)
My question, do you need help weeding out documentation that is no longer correct? While my technical background (no NT, only basic Linux) means that a lot of stuff is over my head, some of the documentation obviously needs pruning and I would be available for that.
A related question: is John Terpstra still in the project?
Re:Windows 2000 Support (Score:2)
Hey Jeremy (Score:2)
Dual Domains (Score:2)
I would like to keep things at a very high level, but I've posed this question to all those whom I know to be very knowledgable about Samba and have yet to get a satisfactory answer. I have 2 questions.
1. My employer uses a dual-domain system where all the user accounts are in one domain and all the accounts for machines are in another. The two domains are incestuously joined with trust relationships. When setting up the Samba Client, is there any way to configure the Samba client to validate credentials to both domains just like the NT boxes on our network?
2. Will the Samba team ever come out with a User Manager or Server Manager for Linux?
Thank You.
Samba TNG, windows 2000, and the Future. (Score:3)
I recently got a Linux server and Windows 2000 clients working with TNG
I figured out how to get the w2k clients into compat mode (because all authencated users no matter what from a nt4 doman become 'User'), but, is there an effort to get w2k domain groups working at all? Is there a hack to get it to work?
Also, I thank you and all of the Samba Team for releasing such a solid product. Samba itself is a great asset to opensource developent and my personal goals to avoid dealing with CALS.
Where can I send [postcards,pizza,beer,etc]?
Unique features (Score:3)
What other unexplored potential do you see in windows filesharing besides what the official "Microsoft Spec" is?
NetBEUI (Score:3)
--
What happens if UCITA passes? (Score:3)
How does the potential use/misuse of these laws affect the future viability of the Samba project?
Samba as a security measure? (Score:3)
I've seen many setups using Samba as an extra level of security in the DMZ of a firewall - using the SMB protocol to keep data synchronized instead of normal Unix file transfer protocols (ie ftp or nfs) that are better known to the cracker community.
Did Win2000 break anything? (Score:3)
Dynamic mounting (Score:3)
My question: When, if ever, do you see samba having a "dynamic mounting" of shares? Possibly a smbshares.conf that is read any each mount specified is monitored for activity. If the share dies, it is unmounted until it is available again, at which time it is remounted.
-------
CAIMLAS
Samba TNG (Score:3)
samba and grander networking schemes (Score:4)
My understanding of, for instance, Mac Services for Windows NT and UNIX Services for Windows NT is that it provides services from the same databases, just with different protocols.
So if you can see where this is going, is there any work on making samba able to make use of network-wide databases for user authentication, share specification (I know it can already use the autohome map, but more than that!), etc.?
In particular, I'm interested in things like:
- Being able to authenticate netatalk, samba, and UNIX users all the same way (i.e., not having smbpasswd, NIS, and
/etc/passwd all need to be updated every time a user changes his password or is added) - Being able to specify at the same time what my file server serve up, via netatalk, samba, and NFS (so I don't edit three configuration files every time I add a share, or move a share)
- Being able to specify from one system what each and every file server serves up, without having to connect to the machine in question and edit the smb.conf by hand (or by web)
Clearly this depends on more than just the samba team, but are there plans to add NIS authentication (i.e., instead of or in addition to smbpasswd), NetInfo authentication, and/or smb.conf NetInfo or NIS databases?Kerberos (Score:4)
Microsoft has apparently molested Kerberos in their latest W2K upgrade, can you clear up some of the confusion about how this will effect samba server->NT.
I've heard their exploitation of the protocol wont effect samba, some say it wreaks havoc, whats the scoop ?
Reverse Engineering SMB (Score:5)
I am sure you could lay a pizza-track from Earth
to Jupiter by now with the money you saved people
who would have had to buy Windows NT-Server.
The issue of reverse-engineering has become a
very *hot* issue recently with the advent of
CSS source-code to authenticate DVD-ROMs and
also descramble the content. My questions:
- How much reverse engineering went into the SMB
and WINS protocols, in contrast to real coding,
say up to the first usable share exported from
a Unix machine?
- Did you peek under Microsoft's hood and examine
some VXDs or NT kernel drivers to get to those
last and hardest 10% of insight?
- How important do you think is the roll-out of
working PDC-code?
- Finally, on the law side of things, there is a
German law that explicitly allows reverse
engineering for the purpose of interworkability.
What has been YOUR legal situation (being "down
under"), has Microsoft ever asked you to stop
your work (BEFORE they needed it in their DOJ
case), or even threaten you with legal action
or a life-time supply of pizza?
Thanks so much,
Stephan Eisvogel
eisvogel(at)hawo.stw.uni-erlangen.de
Don't be fooled by the hype. (Score:5)
Samba? Samba? That word says one thing to me, and one thing only: Some slinky disreputable Latin American gigolo character, skulking around the suburbs and worming his way into the hearts of virtuous women, destroying their lives and moving on. The word "samba" says nothing to me of quality or reliability. Nothing.
So Jeremy, I ask you: Why do you choose to be associated with such a grossly disreputable and frankly immoral product? Why do you choose to spend your days lazing around the Beverly Wilshire, oiling your pencil-thin mustache, langorously sipping mai-tai's and attempting to seduce other men's wives? Aren't you disgusted with yourself and the low state to which you've fallen?
Have you no shame?
ACLs (Score:5)
Will this tie in with the Linux patch to add POSIX ACLs, or will it happen above that layer in a file Samba maintains?
The possibility exists for me to subvert W2K at my place of business if Samba can do this for my users. I hope this happens soon.
VFS (Score:5)
I have been out of the loop for a very long time, but was wondering how things a going with the VFS stuff and if anybody else has picked up on it. The possibilities are endless. One could "share" FTP sites, databases, tape drives, archives (tar, gz, zip) to the masses who use Windows clients while keeping them in the familiar surroundings of the Windows Explorer filemanager.
What are the plans for VFS in SAMBA?
Keep up the good work.
For the Challenge or Outcome (Score:5)
Active Directory vs. LDAP (Score:5)
Samba and Active Directory (Score:5)
Report Comments (Score:5)
I am currently in the process of writing a university-level report for a course I am taking. The topic of the report will be SMB vs. NFS. I am not trying to identify a clearly "surperiour" protocol, I am seeking rather to simply present as much detailed facts/benefits of each and have the reader decide for themselves.
Obviously you would be an ideal person to ask about this topic. What are your feelings as to the advantages SMB has over NFS, if any, and how could the benefits of NFS, if any, be carried over into SMB?
Replacing NT (Score:5)
Perhaps the same question stated differently is what are the long term goals for the project in relation to NT PDC Server compatibility?
Any estimates on how long such compatibility will take?
Thanks again for all the hard work!!