From owner-freebsd-questions@freebsd.org Sat Sep 23 08:44:59 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1045E2AF69 for ; Sat, 23 Sep 2017 08:44:59 +0000 (UTC) (envelope-from timur@bat.ru) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 577B46C821 for ; Sat, 23 Sep 2017 08:44:59 +0000 (UTC) (envelope-from timur@bat.ru) Received: by mail-wm0-x22c.google.com with SMTP id q124so8774656wmb.0 for ; Sat, 23 Sep 2017 01:44:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bat-ru.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=z6YQBXq581igo2BsOhrckJ2cQueLWOkOBhiYwG+/DyI=; b=bOlyAo6Px6MruOr7E5b84A0mGXFpZgLB6vzm81aEX5pqUXa+IyxBq2wmjKKyjQokKe LjsalFCeqSI4WeduYJPzpxGDEIBj0rxtUjeuzsTCoovNKIHVwJEQpq9MtDhJ6stXa/Gc SIAZ5X2iOKKD0A3kw+qFr3qa1QHT2t6Rh+KakWzxM8n2JQi7v14CQfrCpXI+lqU9SZ6k uQGjIuwG36dKnwPUwWsFEfnA6HNVHDsx/flIdnv78emfYgt/exy44Wpt8wnHVARliOO0 VpZ+w351V5YtG8b8hwGh28am1wqq2Fapv16CZXu5cQRCxGQUgcu3nhBK7e67bJ/9XKXe 3Xew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=z6YQBXq581igo2BsOhrckJ2cQueLWOkOBhiYwG+/DyI=; b=t6V7ncUJ7SqY1BfCRALs+9D5SVj650AUR+gF6hdxOeF0PGpiERo7f+J3FPd6npkAB8 L2dmNAJ729/933lXxqq0MbpJlBkTjsdoEjNDYrqJgVJoEJyW0dZpS2nPu0E/JRipRRN2 yuTQhzg24oKjcNgBWOe/TLmC06oP9cyUYcsJ6soaECCqq0EpU4/o2NmOjMWyNAFtbwYi if1diqvzGb/J1R6kVMfmnD7akzct3Kz6IeBdEVRsrsf/g3fUkwc5+xAUDuMCRjA/aLuN Hzl6DXX/p6GqTrWhIOZJHkBWGwcv3+anUHdtwMmdvXT20nF+1wgA3OwOQc7Cp25nQlgj tcyQ== X-Gm-Message-State: AHPjjUh3amZWiseznIBaIQHtot1yLQJIs1nCPkWVoZM9RIsK4eDVvyTq xJNNapznrlzPlkk6K0wgxk+OC1WvsB20/VwvYQUscN1+Er0= X-Google-Smtp-Source: AOwi7QCbfV+bd6pmuWmc8jxGHPePl/SIpmMtE0nIApDZLXZr/KdRpujty1BEeT8bBtclRMMcdf2EJePHr7XmmffMXTA= X-Received: by 10.28.175.197 with SMTP id y188mr5190319wme.20.1506156297030; Sat, 23 Sep 2017 01:44:57 -0700 (PDT) MIME-Version: 1.0 Sender: timur@bat.ru Received: by 10.223.164.144 with HTTP; Sat, 23 Sep 2017 01:44:26 -0700 (PDT) In-Reply-To: <485a5756-ca36-bba6-62c8-c76022b05452@netfence.it> References: <411eb82456c15c41763909673a63208b.squirrel@webmail.harte-lyne.ca> <485a5756-ca36-bba6-62c8-c76022b05452@netfence.it> From: "Timur I. Bakeyev" Date: Sat, 23 Sep 2017 10:44:26 +0200 X-Google-Sender-Auth: C4leWS9l_Sw8HgudzvqZqjgXPCg Message-ID: Subject: Re: Future of SAMBA on FreeBSD To: Andrea Venturoli Cc: FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Sep 2017 08:44:59 -0000 Hi all! Sorry I didn't reply to this thread before, there are too many public channels where Samba and FreeBSD are both discussed, so it's almost impossible to follow all of them. If you want to get the definite answer - please add me to the CC list. Problems with the DC provisioning are around for quite a while, due to various configurations as well as because both samba and FreeBSD are moving targets and code is changing rapidly in both upstreams. The particular raised problem is created by the "fix" in the https://github.com/samba-team/samba/commit/738797d8ad6908de457786cc948dcde151e2b9e1, which, possibly, made things work better with the MacOSX, but entirely broke DC provisioning in Samba 4.6 on FreeBSD. I'm working on the appropriate fix for this problem, which would allow having both DC provisioning and Time Machine working properly on FreeBSD, but as such fix, possibly, will affect the way how particular extended attributes are stored on a file system, I feel it's not safe to bring such changes into 4.6 branch and targeting just released 4.7 for it. There is another long standing issue with the DC provisioning onto ZFS-only installations, where you had to create special volume with the UFS to get things work properly. This issue was fixed by John Hixon from the iXsystems Inc. in the custom version of Samba on the FreeNAS/TrueNAS and from the kind permission of the iXsystems this work will be ported into the FreeBSD ports. With best regards, Timur Bakeyev, sponsored by iXsystems Inc. On Mon, Sep 18, 2017 at 10:02 AM, Andrea Venturoli wrote: > On 09/17/17 23:18, Adam Vande More wrote: > > What? It doesn't seem like you have a good enough understanding to make a >> claim like that. It is quite clear that bug is relavant only to jailed >> instances of samba, and VFS related perms. Your current was already >> explained to you once, and you've been reminded of it. >> > > Sorry to step in like this, but I find the original question quite > interesting. > Since we are using jailed Samba 4.4 instances, I'd be very worried if this > setup would lose support in the future. > > Is there any plan to allow Samba to properly work in a jail? > > bye & Thanks > av. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe > @freebsd.org" >