Maybe there’s an easier way, but this got things working for me :-) Downloading and Configuring SAMBA Xcode-select -switch /Applications/Xcode.app

Prepping Xcodeįirst, download Xcode from the App Store. Here are my observations to getting it to work in 2019. Getting SAMBA to work on High Sierra was not very straightforward. I strongly recommend you use that page as a reference as I’m going to highlight the additional steps. This link provided a really good starting point: I do not have time to baby sit an unreliable server. TimeMachine managed to save the day - I restored the VM disk and got Ubuntu working again. Until ‘fsck’ didn’t work because the file system had been scrubbed so badly. The shared area was living in the OSX domain (so that it was TimeMachined), and a VirtualBox shared folder provided a helpful gateway for the Ubuntu server to access and deliver the files.īut Ubuntu crashed about every week or two… and then the VM drive would be mounted in read-only mode… so ‘fsck’ to the rescue (mostly). By matching up the UIDs within the Ubuntu machine with the Mac mini’s UIDs of the data to be served it all worked pretty well. I ended up installing VirtualBox, with Ubuntu Server doing the SAMBA part. So, it was time to upgrade… First attemptĪfter a week or so of fishing around, it became evident that SAMBA was not going to be a simple MacPorts or Homebrew experience. The Mac mini, coupled with TimeMachine, proved a great choice.Įventually, though Microsoft made it harder to enable SMB v1, then impossible. This ran absolutely wonderfully, using SMB v1, all the while we had WinXP. Oh dear, oh dear!Īfter trying Apple’s Server product on a Mac mini, and failing, I ended up using Homebrew to compile SAMBA. Then SAMBA went GPL licensed and Apple had to develop their own SMB code. My understanding of the history is that SAMBA was originally MIT or BSD licensed - and Apple used it. There’s quite a bit of history to running SMB file sharing on OSX. Photo by Javi Hoffens on Unsplash A little history

Samba mac os