On Wed, 01 Jan 2014, Jakub Bogusz wrote: > On Tue, Dec 31, 2013 at 07:32:27PM +0100, Jan Rękorajski wrote: > > On Tue, 31 Dec 2013, qboosh wrote: > > > > > commit 2948c518df0a1cdc2672a30e14a7138de4b0a5bc > > > Author: Jakub Bogusz <qbo...@pld-linux.org> > > > Date: Tue Dec 31 19:26:50 2013 +0100 > > > > > > - all samba/vfs modules belong to samba3 exclusively; samba4 uses > > > different ntvfs interface > > > > Oh, you are so wrong. Revert this commit. > > Did you deployed this software anywhere? AD functionality will not work > > without those few vfs modules. > > Uhm. > The only place where I can see reference to vfs modules is: > > samba-4.1.3/source3/smbd/vfs.c: status = > smb_load_module("vfs", module_path); > > which is part of libsmbd_base, referenced only in source3 directory. > > What is the path of using them from samba4/AD?
Can't tell you, due to those libs being intertwined to the point of complete mess. What I can tell that I did try the change you made and samba told me that system lacks xattr/acl support and AD will not function properly. Maybe something changed recently, but I'm not too keen on lerning it the hard way. I based samba4 packaging on debian, so check there if you want. But whatever you do please test this package before bumping release or sending build requests (simple `samba-tool domain provision ; service samba start` should do the trick). -- Jan Rękorajski | PLD/Linux SysAdm | http://www.pld-linux.org/ baggins<at>mimuw.edu.pl baggins<at>pld-linux.org _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en