similar to: Samba Netatalk VFS module changes with 2.0.1

Folks, FYI. -- John H Terpstra Email: jht@samba.org ---------- Forwarded message ---------- Date: Thu, 17 Apr 2003 14:47:50 +0000 (GMT) From: John H Terpstra <jht@samba.org> To: Malte Weber <m_weber@wiwa.de> Cc: samba-technical@samba.org Subject: Re: netatalk/samba On Thu, 17 Apr 2003, Malte Weber wrote: > Hi John, > > I unfortunately wasn't able to attend SambaXP,

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

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: >

Reply-To: Hi When configuring samba there is an option to turn on netatalk-support. I did this, because we need to see the shared on both windows and mac, but I couln't see any difference in sambas behaviour. Netatalk stored the ressource-fork, and some files the Mac-Finder created in Directories calles ".AppleDouble". I hoped, that with netatalk-support samba would handle those

Hi HAT! Nice to meet you over here... ;) On Wed, Mar 11, 2015 at 11:30:45PM +0900, HAT wrote: > 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. >

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

I recently took over a x86_64 CentOS 4.0 server running an "unsupported" kernel. On examining the box it seems that perhaps it is because of the use of xfs and netatalk. I would like to update the box to 4.3. I think I can do away with the netatalk, but doing away with xfs would require a substantial amount of work. Questions: 1: In reading the archive of this list there was a post

hi list, i searched bugzilla but couldn't find an open/fixed bug for my problem: [system] - AMD Opteron 248, 8GB - SuSE 9.1 Prof. x86_64 - Samba v3.0.11-2.1 from ftp.samba.org (ftp://ftp.samba.org/pub/samba/Binary_Packages/SuSE/3.0/x86_64/9.1/) - netatalk v2.0.2 (self compiled) [situation] we're accessing our samba fileserver (files, directories, ... ) from different platforms

I've just done a: ./configure --with-netatalk --with-mmap --with-ssl --with-quotas on my Linux 2.0.36/intel server... built samba 2.0.3 [release] successfully testparms is happy, my WinDoze clients are working smoothly (good job, Samba dudes!) I notice the netatalk.c file never gets compiled, doing mass-grep's (in all source/lib directories) on WITH_NETATALK don't show any

I forward this message, because, my problems, are the same: Ciao: Fonya Hi everyone, This has already been addressed a couple of times, but none of the solutions proposed up to now seem to help in my installation (I've already tried the samba settings suggested by =R= on 16 Jun 99, to no avail). I have a Linux box running SuSE 6.0 and kernel 2.2.10, netatalk-1.42b2+asun2.1.3, and

hi@all i'm using netatalk and samba as fileserver for different clients (OS9,X,WinNT/2K/XP) to create shares, that are visible and accessible for all clients (via afp/smb) i created a folder and made it public in all daemons (atalk, samba) to get a better file handling i'm using the samba feature: vfs object = netatalk but there are still some problems files that are created via afp

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 =

I've just noticed that --with-netatalk and --with-quotas are options to configure for samba. Is anyone using these options on Solaris 7, and what do they do and how well ? I'd really like to display a users quota as "disk size" and their remaining space as "disk free". Is --with-quotas the right way to go about this ? I also run netatalk. Do I need to use

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

Hi, I've got a SuSE 9.0 running Samba 3.0.1 and Netatalk 1.6.3 Samba is a member server of a win2k domain, I'm using winbind to authnticate my users. Well, with the Windows users, everything is ok. But not with the Mac users I'd like to setup Netatalk to authenticate my Macs against the win2k domain as with Windows. Is this possible? I've sarched the web all around and

Hi all, I'm have a Linux Box running samba and netatalk, and a file system shared with Mac and Windows users. My problem is that when a user in Windows delete a file that have a Macintosh label (color), and later the Windows user put another version of the file with the same name, the Macintosh label still apear (and this is not the behavior that i need). I view in the file system that

I am having difficulty getting Netatalk to authenticate using NT Domain via Winbind. I have Samba successfully installed, and winbindd is working and running. (Tested via wbinfo) I have placed pam_winbind.so in the /usr/lib/security directory, and have installed netatalk with the --with-pam option, but I still cannot seem to get it working. Any help would be appreciated. John Helt Systems

It might help if you view the default directory ACLs using the getfacl utility. These are what will be inherited by stuff created in the lower directories. I would ask yourself if you actually need ACLs at all. The Samba share permissions are pretty thorough and life is far easier without ACLs as you can clearly see what permissions are in use and backups are not an issue. ACLs can quickly

hello all... i'm running freebsd 4.8 release on our fileservers. we serve files to over 50 macintosh OS 9 clients, and we use netatalk to do it. However, all our username/password info is managed by the corporate IT dept. and they run Win2000. To avoid having to maintain my own password database, I'd like to use the authentication mechanism built into samba to authenticate our

On Fri, Dec 18, 2015 at 02:20:54AM +0900, HAT wrote: > Thu, 17 Dec 2015 18:05:33 +0100, Ralph Boehme <rb at sernet.de>: > > iirc you need fruit:encoding = native > > Solved. Thanks! > I'm looking forward to netatalk 3.1.8. > > $ getfattr Mew.txt > # file: Mew.txt > user.com.apple.TextEncoding > user.com.apple.metadata:kMDItemFinderComment > >