Like in the years before you can use these instructions to create an installer USB stick with OS X Sierra on it.
I’ve moved my iTunes library from my Macbook’s SSD to my Synology NAS on a network share. This is quite easy and can be made inside the iTunes preferences pane. After you’ve changed the path for the iTunes Media, all iTunes managed media will be moved to the new location (assuming you let iTunes manage your files of course :)).
This allows you to have your iTunes library on your Macbook while all the large files are stored on the NAS. This is especially important for larger libraries as well as the newer Macbooks which only have a limited flash drive instead of larger harddisks.
However, there is one important problem with this solution: Once you’ve disconnected from this network share for whatever reasons and you try to start iTunes, you’ll have your iTunes Media folder reset to your user’s music folder on your boot disk. You’ll now need to reset the path to your files again, and this will again cause iTunes to check all files if they are on the right location and moves them if necessary.
I thought I’ve taken care of this problem with auto connecting to the network share with a Login Item. However, this didn’t help me much since I sometimes have disconnections to my network (e.g. when I’m on the road) and the network connection will only be created once during the login of your current user. So this doesn’t help me at all and caused me to look for another better solution.
So I’ve found
this gist (the link is dead) and modified it a little bit to my environment. Therefore here’s my short list of modifications for using autofs in combination with AFP or SMB volumes:
If you now start up iTunes again, it will try to locate the media files in the /Volumes/music folder, like I manually specified it. However, autofs will now automatically mount the network share for me and iTunes won’t complain about a missing volume. This way I won’t ever need to take care of manually updating the path once I forgot connecting to my NAS 🙂
Hm, it seems that the trick with /../Volumes does not work anymore on Mac OS 10.11.4 🙁 If I try to list the content of the mounted volume an error message is returned:
ls: : Unknown error: 118
So I need to mount the volume in a different folder and need to change the path in iTunes again.
I’m not able to mount afp volumes anymore so I’m using smbfs like it is described here. However, this will require a user and password in the configuration file 🙁
Mac OS Sierra breaks the autofs configuration. I had to change it a little bit according to this SuperUser entry. The Gist is updated accordingly.
My current network setup allows me only to use small bandwidth connections between the living room (that’s where my Raspberry Pi is used as my Mediacenter) and office (my NAS). However, my Macbook is fast enough and can access the NAS wirelessly, so that I often use it as a replacement for the hardwired Raspberry Pi.
However, I cannot use my Hyperion Ambilight setup behind the TV in combination with the Macbook, because its only connected to the Raspberry Pi. But yesterday I’ve found this plugin which enables the Kodi setup on my Macbook to connect to the Hyperion Server on my Raspberry Pi over network.
- Download the zip file with the content of the git repository.
- Start Kodi on the Macbook and install it using the add on manager. You can point to the zip file directly without the need to unzip it first.
- Configure the installed plugin to connect to the ip of your Hyperion server.
- Start a video and be amazed that the lights on your TV will work wirelessly 😉
It’s unbelievable: Microsoft Office Mac 2011 cannot open files from network folders when the share name contains „home“. My Synology NAS uses shared folders for each of its users. The user folders can be reached under the „home“ share and are automatically mapped to the user’s home folder on the Synology. This is the default setting for every new standard setup of Synology NAS.
I’ve tried recently to access an Excel file from my home folder. After double clicking in the Finder, Excel opened with this error message:
So it cannot find the file. This is due to a known Office bug that exists now for several years and appears to be still unpatched.
It’s inexplicable how an error of this severity is still unpatched. All my search results suggest me to stop using the home folder and use instead a different name. That’s working for my user, because it has admin rights and can open the „homes“ share with a subfolder to my username. However, not all of the users on my network should have this right.
I only hope that the new Mac Office will address this issue. The currently available preview is pretty unusable and tends to crash when I’m working with network volumes.