<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel>
	  <title>Ask MetaFilter questions tagged with multiusers</title>
      <link>http://ask.metafilter.com/tags/multiusers</link>
      <description>Questions tagged with 'multiusers' at Ask MetaFilter.</description>
	  <pubDate>Fri, 09 Mar 2007 09:41:00 -0800</pubDate> <lastBuildDate>Fri, 09 Mar 2007 09:41:00 -0800</lastBuildDate>

      <language>en-us</language>
	  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
	  <ttl>60</ttl>	  
	<item>
	<title>Packing two users/computers into one</title>
	<link>http://ask.metafilter.com/58396/Packing%2Dtwo%2Duserscomputers%2Dinto%2Done</link>	
	<description>I&apos;m consolidating two Mac computers with unique users onto one new machine. What&apos;s my best process for setting up the users so that they can share iTunes and iPhoto libraries? Should I create the admin account and add the two users separately or let one of the users (the power user) be the admin account and add the non-power user as a non-admin? My primary concern is to make it easy to migrate their existing data over to the new machine and to consolidate their iTunes and iPhoto libraries so they can both use the same libraries for those apps.&lt;br&gt;
&lt;br&gt;
Are there any issues with putting the iTunes library in a shared folder when it comes to permissions? They both have their own iPods and I want them to be able to purchase, add playlists, etc., off the shared library.</description>
	<guid isPermaLink="false">tag:ask.metafilter.com,2007:site.58396</guid>
	<pubDate>Fri, 09 Mar 2007 09:41:00 -0800</pubDate>
	<category>iphoto</category>
	<category>itunes</category>
	<category>mac</category>
	<category>multiusers</category>
	<category>shared</category>
	<dc:creator>strangeleftydoublethink</dc:creator>
	</item>
	
	</channel>
</rss>

