<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 4 Jun 2014, at 15:53, Joseph Fry <<a href="mailto:joe@thefrys.com">joe@thefrys.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Sounds like a weird question, so let me elucidate!<br>
<br>
On my mythtv box, I have a directory which contains all my ripped<br>
CDs. This is shared via nfs and samba so that all other machines<br>
(there's windows and linux clients) in the network can access them<br>
to play music. Let's call this /myth/music.<br>
<br>
The issue is that when this area is shared with iTunes, iTunes<br>
insists on putting the downloaded podcasts in /myth/music/Podcasts.<br>
There is no configuration for the podcasts location, it always puts<br>
it at one level below your music. This is fine for a single user.<br>
<br>
The problem comes when several people want to use iTunes to access<br>
the music and load their own podcasts, because the podcasts area is<br>
also shared via the same location for all users.<br>
<br>
Therefore I need everyone to access /myth/music as a shared area,<br>
but everyone needs to be able to access /myth/music/Podcasts as a<br>
different area to all the other users.<br>
<br>
I've tried Googling this, but not come up with the right combination<br>
of vague words to find a solution here.<br>
<br>
The only way I've thought of to work round this so far is to maybe<br>
create /myth/music/Podcasts as a symbolic link to /local/Podcasts,<br>
which is outside of /myth/music, and then share /myth/music out to<br>
different Linux boxes, and each user obtains /myth/music from a<br>
different server, all of which have a different /local/Podcasts.<br>
This sounds like it should work, but I haven't tried it yet.<br>
<br>
I don't want to duplicate the music - there's over 15,000 tracks in<br>
there, and the collection is not fully online yet! This would be a<br>
major waste of disk.<br>
<br>
Can anyone think of any other way of doing this so that each user<br>
can share a single copy of the music and have a local copy of<br>
podcasts, given the invariance in the iTunes setup for the location<br>
of the podcasts?<br></blockquote></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"></blockquote>You could just a set of shares for the podcasts, then on each machine mount the normal music share at /myth/music and /myth/music/Podcasts could be the users individual share of podcasts.<br>
<br>Alternatively you might be able to do something creating with autofs, but its probably more trouble than its worth for a small setup, especially when its probably going to be fairly static.<br><br></blockquote><div><br>
</div><div>This is immediately what I though too. <br><br>On server:</div><div>Create an export for /myth/music, <br>Create /myth/podcast-bob and /myth/podcast-jane directories and exports. <br><br></div><div>On Bob's client:</div>
<div>create /home/bob/music folder<br>mount /myth/music to /home/bob/music</div><div>mount /myth/podcast-bob, /home/bob/music/Podcast as desired.<br><br>I don't believe that NFS would have any issue with nesting a mount inside another mount like this, after all the OS just treats it as another filesystem and every linux system I have ever seen does this (/dev, /proc, etc).<br>
<br>The one caveat would be that on the server, the data doesn't have the proper structure. This can be easily remedied by storing your data elsewhere and mounting the folders to the appropriate location. For example: store your data in /home/shared/music, /home/shared/podcast-bob, and /home/shared/podcast-jane. Then on the server you can use normal folder mounts, not NFS, to mount /home/shared/music to /myth/music and /home/shared/podcast-bob to /myth/music/Podcasts.</div>
<div><br></div></div></div></div></blockquote><br></div><div>The OP mentions iTunes, which implies either Mac or Windows clients, whilst the above would work for Mac clients it’ not going to work for Windows clients.</div><div><br></div><div>I’d approach it like this, </div><div> 1. configure samba to share users home directories</div><div> 2. under each users home directory create a private/podcast directory structure</div><div> 3. create a combined view of private/podcast and /myth/music called music within each users home directory using aufs</div><div> mount -t aufs -o br=/myth/music:/home/user1/private none /home/user1/music/</div> mount -t aufs -o br=/myth/music:/home/user2/private none /home/user2/music/<div> (repeat for each user)</div><div><br></div><div>this should (I’ve not actually tested it) create </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>/home/user1/music/* - all the files from /myth/music</div><div> /home/user1/music/podcast - this users private/podcast directory</div><div><br></div><div>Now this isn’t going to scale very well for a large number of users but it should be fine for a dozen or two.</div><div><br></div><div>One thing to note is that I don’t believe iTunes likes to share it’s library, when I tried between my two Mac’s using NFS if I opened two clients at once it corrupted it’s database files.</div><div><br></div><div>Regards</div><div> Russell</div><div><br></div><div><br></div></body></html>