I know that sounds boring (and it is:) ), but because of it I could update the smb-enum-users functions to search for far more users at once without using any more outgoing bandwidth. Instead of checking for one user at a time, I can check for 10 (or 30, or 100). Try mount volume 'smb://forman@vortex/local' mount volume 'smb://forman@vortex/scratch' end try Save the script as an application using the Script Editor and put it in System Preferences - Accounts - Startup Items to mount the drives when you log in. In this Instructable you will learn how to backup a mac to a Windows Home Server box or any other SAMBA share. Mac can t download anything else. You will need: Windows Home Server (Or an SMB network share) with free space as big as your mac's HDD used space Apple computer running 10.4 or 10.5 Network Connection between the two I have not tried this with 10.4 Tiger, but i know its much easier than Leopard.
Mac Smb ConnectionEnable Smb On Mac
Hi, I'm looking to share a dataset from my FreeNAS 11.1 server to my Mac and Ubuntu machines, I currently have no Windows machines and don't plan to, at least for the foreseeable future.
From reading around a bit, I think an SMB share is my best option. I tried setting up a dataset with 'share type Windows' and sharing this via SMB, and it works ok to mount and read/write normally from mac/linux, but I had problems rsync'ing to it*, presumably because 'rsync -a' wants to preserve permissions and these are different to the Windows permissions on the share. This is a problem since generally I'd like to preserve my unix files' metadata and I'd like to use rsync. This link says that using sudo with rsync will work, but it sounds like a bad workaround (doesn't really tackle the problem of different permissions styles) and besides that I don't necessarily have the option of sudo for all users. I also tried with 'share type Unix' being shared with SMB. This seems to work fine (including rsync), but this forum thread and this docs comment say that it is not recommend. The caveats mentioned in the first (forum thread) link are not listed (I didn't want to resurrect an old thread to ask), but I believe it's due to Unix permissions not supporting Windows ACLs. My questions are: 1) Is this the only caveat? and 2) If so, am I'm right in thinking that this can never cause problems if I never use Windows? Cheers! Edit to add: *rsync error was: `rsync mkstemp operation not permitted` Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |