Aperture 3 - multiple libraries oddness

Discussion in 'Digital Photography' started by Westside guy, Feb 13, 2010.

  1. Westside guy macrumors 601

    Westside guy

    Joined:
    Oct 15, 2003
    Location:
    The soggy side of the Pacific NW
    #1
    Just a quick note about something that seems rather silly to me. I can easily export a folder to create a separate library - this is great because it'll let me easily segregate my work images from my personal images.

    So I exported my work folder (which contains a bunch of projects) to a network drive that's being shared via AFP from my main Linux box - no problem at all. But, when I try to open that new library, Aperture complains that it's on an "unsupported file system" and refuses to open it!

    If it's not going to let me open a library that exists on that file system... why the heck did it let me create it there in the first place? :eek: :rolleyes: :D
     
  2. TuffLuffJimmy macrumors G3

    TuffLuffJimmy

    Joined:
    Apr 6, 2007
    Location:
    Portland, OR
    #2
    Because it can write to that file system (due to the network) but it can't execute code in that file system.


    Just my guess.
     
  3. Westside guy thread starter macrumors 601

    Westside guy

    Joined:
    Oct 15, 2003
    Location:
    The soggy side of the Pacific NW
    #3
    I appreciate the reply - however there's no code execution involved in reading a file off a disk.
     

Share This Page