Date: Sat, 7 Sep 2024 20:18:44 +0200 From: Stefan Esser <se@FreeBSD.org> To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD+samba as a time machine server for OSX/Sonoma? Message-ID: <54eef546-25c7-452a-ab52-7e39b133cdee@FreeBSD.org> In-Reply-To: <D6787C09-DFF2-4FA4-9F07-6167322D1A78@freebsd.org> References: <0.2.0-final-1725702660.839-0xb11c62@qmda.emu.st> <D6787C09-DFF2-4FA4-9F07-6167322D1A78@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 07.09.24 um 14:18 schrieb David Chisnall: > On 7 Sep 2024, at 10:51, Mark Delany <x9k@charlie.emu.st> wrote: >> >> I'm going to ask a silly question here. But why are people running samba instead of >> netatalk if they are only using the timemachine backup capability? > > Does AFP still work with newer versions of macOS? I thought they removed support for it with APFS. I have both Samba and NetATalk installed and running on my home-server. Timemachine baclkups are working well using samba-3.16, but fail with samba-3.19 (corrupting the backup!). I have used netatalk for timemachine backups, do not remember why I went back to using samba. Maybe I should try using netatalk again, since then I could update samba to 3.19 for other file systems. BTW: vscode on the MacBook does not work well on directories exported using netatalk. Every "file safe" operation warns that the target file had been modified and asks for confirmation to overwrite it. I have not tried to diagnose this issue, since it works well when using samba to access these directories. Best regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54eef546-25c7-452a-ab52-7e39b133cdee>