search for: vfsfruit

Displaying 9 results from an estimated 9 matches for "vfsfruit".

Did you mean: vfs_fruit
2018 May 13
0
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
2018 May 17
0
move from netatalk to samba + vfsfruit
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
2018 May 17
0
move from netatalk to samba + vfsfruit
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
2018 May 17
0
move from netatalk to samba + vfsfruit
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
2018 May 13
2
move from netatalk to samba + vfsfruit
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 with samba and write them back in the new format? afp.conf: appledouble = ea ea = samba
2018 May 17
1
move from netatalk to samba + vfsfruit
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: >
2018 May 17
2
move from netatalk to samba + vfsfruit
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
2018 May 17
2
move from netatalk to samba + vfsfruit
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. > > >
2018 May 17
2
move from netatalk to samba + vfsfruit
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