similar to: move from netatalk to samba + vfsfruit

Am 13.05.2018 um 12:11 schrieb Reindl Harald via samba: > since "ea = samba" was only added to very recent netatalk versions and > so don't apply to files with a history of many years what is the way to > go get rid of netatalk these days? > > is there still no tool to read/write the existing netatalk appladouble > extended attributes which are *not* compatible

On Sun, May 13, 2018 at 12:51:14PM +0200, Reindl Harald via samba wrote: > hell, what is the way to go switch all clients using samba without lose > data like old fonts which have important data in the resource fork > *without* create a new share and copy all data from a Apple client > around what takes ages, changes fileowner and is difficult when the > admin is a Linux user with

On Thu, May 17, 2018 at 04:49:11PM +0200, Reindl Harald via samba wrote: > > > Am 17.05.2018 um 16:17 schrieb Ralph Böhme: > > On Thu, May 17, 2018 at 03:44:12PM +0200, Reindl Harald via samba wrote: > >> Am 17.05.2018 um 14:22 schrieb Ralph Böhme: > >>> iirc the only thing that is currently not working is cross-protocol xattrs for > >>> xattrs

On 26/12/15 17:08, HAT wrote: > Hi, > I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > > The EAs are not seen from clients yet. > > smb.conf: > path = /export/test1/ > writable = yes > vfs objects = catia fruit streams_xattr > fruit:locking = netatalk > fruit:encoding = native > streams_xattr:prefix = user.

On Thu, May 17, 2018 at 03:44:12PM +0200, Reindl Harald via samba wrote: > Am 17.05.2018 um 14:22 schrieb Ralph Böhme: > > iirc the only thing that is currently not working is cross-protocol xattrs for > > xattrs created via Netatalk without ea=samba. I have a WIP patch for Samba here > > [1], but that would require a *lot* more thinking, hacking and testing. > > >

Hi. I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. I confirmed that ResourceFork and FinderInfo are compatible with Netatalk 3.1.7. However, EAs are incompatible. The character ":" in EA name is wrong. The EAs are not seen from clients. smb.conf: [test2] path = /export/test2 writable = yes vfs objects = catia fruit streams_xattr fruit:locking =

On Fri, Dec 18, 2015 at 01:14:25AM +0900, HAT wrote: > Hi, > > >> not sure, but the colon in xattr names is probably not handled > >> correctly at this point. Can you please file a bugreport so we can > >> track this? > > > > Bug 11162 > > https://bugzilla.samba.org/show_bug.cgi?id=11162 > > I tested samba 4.3.1 on Fedora 23 and rawhide.

> not sure, but the colon in xattr names is probably not handled > correctly at this point. Can you please file a bugreport so we can > track this? Bug 11162 https://bugzilla.samba.org/show_bug.cgi?id=11162 -- HAT

On Sun, Dec 27, 2015 at 02:33:10AM +0900, HAT wrote: > Sat, 26 Dec 2015 17:22:56 +0000, Rowland penny <rpenny at samba.org>: > > On 26/12/15 17:08, HAT wrote: > >> Hi, > >> I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > >> > >> The EAs are not seen from clients yet. > >> > >> smb.conf: > >> path =

On Thu, May 17, 2018 at 05:01:57PM +0200, Reindl Harald via samba wrote: > > > Am 17.05.2018 um 16:56 schrieb Ralph Böhme: > > On Thu, May 17, 2018 at 04:49:11PM +0200, Reindl Harald via samba wrote: > >> > >> Am 17.05.2018 um 16:17 schrieb Ralph Böhme: > >>> On Thu, May 17, 2018 at 03:44:12PM +0200, Reindl Harald via samba wrote: >

Am 17.05.2018 um 14:22 schrieb Ralph Böhme: > On Sun, May 13, 2018 at 12:51:14PM +0200, Reindl Harald via samba wrote: >> hell, what is the way to go switch all clients using samba without lose >> data like old fonts which have important data in the resource fork >> *without* create a new share and copy all data from a Apple client >> around what takes ages, changes

On 26/12/15 17:33, HAT wrote: > Sat, 26 Dec 2015 17:22:56 +0000, Rowland penny <rpenny at samba.org>: >> On 26/12/15 17:08, HAT wrote: >>> Hi, >>> I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. >>> >>> The EAs are not seen from clients yet. >>> >>> smb.conf: >>> path = /export/test1/ >>>

Am 5/30/20 um 8:00 PM schrieb Martin Steiner / 3MF GmbH via samba: > I changed the configuration and raised the log level, in my opion samba tries to access the non existent double files. > Samba is now probably writing the data in a netatalk compliant way in the extended attributes of the file but is not reading it. > > new configuration: > > [Global] > min protocol = SMB2

In case of OS X 10.9 and later, any file could not be removed. $ rm test.txt rm: test.txt: Resource busy cannot remove: OS X 10.11.2 El Capitan OS X 10.10.5 Yosemite OS X 10.9.5 Mavericks can remove: OS X 10.8.5 Mountain Lion OS X 10.7.5 Lion OS X 10.6.8 Snow Leopard Windows 7 Environment: Fedora rawhide samba-4.3.3-0.fc24 smb.conf: [global] workgroup = LOCALNET server string

I worked with Netatalk for years and want to switch to Samba now. Currently i use Ubuntu 20.04. and Debian 9 before, i had no issues with netatalk at all. As soon as i try to add a color tag (e.g. yellow) with Mac OS 10.15.5, the tag appears shortly but hides one second later. The file system is ZFS with no special options configured. I tried the Ubuntu package but also the builds from source

Am 17.05.2018 um 16:56 schrieb Ralph Böhme: > On Thu, May 17, 2018 at 04:49:11PM +0200, Reindl Harald via samba wrote: >> >> Am 17.05.2018 um 16:17 schrieb Ralph Böhme: >>> On Thu, May 17, 2018 at 03:44:12PM +0200, Reindl Harald via samba wrote: >>>> Am 17.05.2018 um 14:22 schrieb Ralph Böhme: >>>>> iirc the only thing that is currently not

Am 17.05.2018 um 16:17 schrieb Ralph Böhme: > On Thu, May 17, 2018 at 03:44:12PM +0200, Reindl Harald via samba wrote: >> Am 17.05.2018 um 14:22 schrieb Ralph Böhme: >>> iirc the only thing that is currently not working is cross-protocol xattrs for >>> xattrs created via Netatalk without ea=samba. I have a WIP patch for Samba here >>> [1], but that would require

Hi, i'm running Samba 4.2.1 compiled from source on an Ubuntu 10.04.4 LTS Server. ACL/XATTR is active and working. I tried to activate the vfs_fruite module and added the sample code: vfs objects = catia fruit streams_xattr fruit:resource = file fruit:metadata = netatalk fruit:locking = netatalk fruit:encoding = native to the share. In addition i tried the following share definition: vfs

When copying files to a Windows 10 client, an error is thrown if the file has extended attributes. In this case, the files were all created by an OS X client with netatalk. I'm using Samba from the Ubuntu 16.04 repository, which is currently 4.3.11+dfsg-0ubuntu0.16.04.11. In my smb.conf: # Netatalk configuration vfs objects = catia fruit streams_xattr fruit:encoding = native

Hello all, I’m trying to use samba 4.5.8 as a file server for my Macs (all 10.12.4 now), as a replacement for netatalk. I did setup smb.conf as suggested # # Options for macOS # http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS <http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS> # ea support = yes vfs