Get Samba version or capability information from Windows

Volker Lendecke Volker.Lendecke at SerNet.DE
Thu Jan 17 21:21:46 GMT 2008

On Thu, Jan 17, 2008 at 07:06:52PM +0100, Corinna Vinschen wrote:
> > Hmmm. This would mean that we have to define features
> > and/or bugfixes. This is a bit too volatile for my taste. We
> That was just a first idea.  Maybe there is no need for a feature
> flag on the file system level, given the existance of
> SMB_FS_ATTRIBUTE_INFORMATION.  But bugfix flags would be very helpful.
> This would not be changed very often, only if the behaviour changes in a
> major way on the client level.  For instance, something like the fact
> that right now the number of links to a dir is set to st_nlink - 1, but
> in a later version it's set to st_nlink or to 1, would call for such a
> flag.  Or perhaps if stuff like the inode number of symlinks change (see

That's also a bit too specific for cygwin I think. We have
tons of bug fixes in every release, along with new bugs
and/or features. Who decides which feature/bug ends up being
codified in some flags field? I think the best we can offer
here really is the Samba version string.

> Maybe, but that's much less reliable, isn't it?  The version number and
> earlier/later dependencies would have to be calculated from an arbitrary
> version string.  There's also no magic which would allow to identify
> that this is a Samba server at all.  Sure, it would be better than
> today, but still...

We can always prefix the version string with a magic number,
no problem.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :

More information about the samba-technical mailing list