Hi all Samba OS/2 users. I've just added OS/2 style extended attribute support into the SAMBA_3_0 subversion branch code. This depends on the underlying OS supporting EA's and (on linux) the filesystem being mounted with the "user_xattr" mount option and the parameter "ea support = yes" being set in smb.conf. Please check out this code and test it - let me know if there are any errors with using OS/2 EA's with Samba3 and I'll try and get them fixed before 3.0.14. Thanks, Jeremy
Jeremy Allison wrote:
> Hi all Samba OS/2 users. I've just added OS/2 style
> extended attribute support into the SAMBA_3_0 subversion
> branch code.
Great!
> This depends on the underlying OS supporting EA's and
> (on linux) the filesystem being mounted with the "user_xattr"
> mount option and the parameter "ea support = yes" being set
> in smb.conf.
What about FreeBSD as a server?
bye & Thanks
av.
Jeremy Allison wrote:> Hi all Samba OS/2 users. I've just added OS/2 style > extended attribute support into the SAMBA_3_0 subversion > branch code. > > This depends on the underlying OS supporting EA's and > (on linux) the filesystem being mounted with the "user_xattr" > mount option and the parameter "ea support = yes" being set > in smb.conf. > > Please check out this code and test it - let me know if there > are any errors with using OS/2 EA's with Samba3 and I'll try > and get them fixed before 3.0.14. > > Thanks, > > JeremyOk, so this is the situation: _ up to yesteday I had to stick to the old, unsupported, unsecure 2.2.12 release, since 3.x showed compatibility problems with OS/2; _ now I tryied 3.0.12_1.1 using the FreeBSD port: the compatibility problem is there again. Everything works from the command line, but the WorkPlace Shell cannot work with remote shares. Extended Attributes also don't seem to work: if I do COPY xxx G:, then COPY G:xxx, they are gone. _ then I tryied compiling myself (no patches) samba 3 SVN: if I leave EA support off everything works from command line and WPS like with 2.2 (this is enough for me, although the more the better). If I turn on EAs, the WPS can still browse shares, but I cannot copy any file *to* them; command line works fine. In any case EAs don't work (see above); I guess this is normal, since EA support on FreeBSD is added with port patches. So, the conclusions are: _ EAs just don't work on FreeBSD; _ I'm left with the doubt wether the WPS bug is gone after 3.0.12 or it is introduced with the FreeBSD patches; I'll wait until 3.0.13 is incorporated in the port tree and check again. Thanks to everyone. bye av.
Jeremy Allison wrote:> Ok, I've taken a look at this and what happens is the client > creates the file AUTOEXEC.BAT and then tries to set a couple of > EA's on it using a trans2 setfilepathinfo with an info level of 2 > (SET_EA). > > Doh ! I've just spotted the problem. Here is the patch (also checked > into SVN) ! We weren't finishing with the call as soon as we'd set > the EA. Thanks....It is me who must thank you. However, I started from scratch, downloading the lastest 3_0 wia SVG, configured id, issued "make" and here's what I got: lib/system.c: In function `sys_getxattr': lib/system.c:1379: error: `EXTATTR_NAMESPACE_SYSTEM' undeclared (first use in this function) ... lib/system.c:1379: error: `EXTATTR_NAMESPACE_USER' undeclared (first use in this function) lib/system.c: In function `sys_lgetxattr': lib/system.c:1406: error: `EXTATTR_NAMESPACE_SYSTEM' undeclared (first use in this function) lib/system.c:1406: error: `EXTATTR_NAMESPACE_USER' undeclared (first use in this function) ... And so on. I understand that all the patches you mentioned in this thread were integrated... isn't it so? bye & Thanks av.
On Sun, Apr 10, 2005 at 03:56:33PM +0200, Andrea Venturoli wrote:> Jeremy Allison wrote: > > >If you SVN checkout it should be fixed now. Sorry for the problem. > > No problem and many thanks. > > Now I was able to compile, but I get exactly the same behaviour as > before: with ea support turned on, I get no EAs if I copy something via > command line, while WPS copy still fails with an error. > I can provide another tcpdump if needed.I could do with a capture trace plus a debug level 10 log covering the same activity. Remember to capture all the packet length and send the raw capture, not a text reprepsentation of it. Thanks, Jeremy.