How to move storage OEMs to Samba 4.0 ?

Alexander Bokovoy ab at
Sat Jun 23 00:23:18 MDT 2012

On Sat, Jun 23, 2012 at 1:40 AM, Andrew Bartlett <abartlet at> wrote:
> On Fri, 2012-06-22 at 08:35 -0700, Jeremy Allison wrote:
>> On Thu, Jun 21, 2012 at 10:10:16PM -0400, simo wrote:
>> >
>> > I would say also that the actual vfs ABI should not change, that doesn't
>> > mean the rest of samba internal are untouchable, but why penalize people
>> > that use exclusively the VFS interface as published ?
>> >
>> > I generally agree with all, although I would prefer if we made an effort
>> > not to change the VFS ABI in a minor release. I am not to ask to be
>> > strict about that, the vfs is large enough that we may not hold to the
>> > promise, but I would like to avoid seeing deliberate ABI change without
>> > a good reason .. "because we can"
>> I agree. I wouldn't break the ABI without good cause also, but
>> we only promise API compatibility, just like the Linux kernel
>> and for the same reason.
> What is the VFS API?
> Does it include all the other Samba functions that a VFS module could
> potentially call?
> (As an example of what I mean, a passdb module AB wrote recently started
> calling become_root()/unbecome_root())
The module does not call become_root()/unbecome_root(). Instead, the
callback for smbldap SASL bind operation is called under
become_root()/unbecome_root() from within smbldap code. All passdb use
is actually done with become_root()/unbecome_root() already.

/ Alexander Bokovoy

More information about the samba-technical mailing list