<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to EXAMPLES</title><link>https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/</link><description>Recent changes to EXAMPLES</description><atom:link href="https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 21 Nov 2012 11:08:10 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage EXAMPLES modified by Xian Su</title><link>https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/</link><description>&lt;pre&gt;--- v4
+++ v5
@@ -32,7 +32,7 @@
     3. Run oinklink:
         /path/to/oinklink.py -or- oinklink (if you did the optional step in #1)
 
-        See oinklink.png in the wiki.
+        See oinklink.gif in the wiki.
 
     You'll notice in my example that some files are green and some are red. The green ones 
     are matched files and red ones are unmatched. This is correct as I do not keep jpg's or
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Xian Su</dc:creator><pubDate>Wed, 21 Nov 2012 11:08:10 -0000</pubDate><guid>https://sourceforge.net3631f5cfc609441d4f190e3369b127957c16e98d</guid></item><item><title>WikiPage EXAMPLES modified by Xian Su</title><link>https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/</link><description>&lt;pre&gt;&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Xian Su</dc:creator><pubDate>Wed, 21 Nov 2012 11:07:50 -0000</pubDate><guid>https://sourceforge.net865c0b3135d96d168b66b90e1357bd75780a1c14</guid></item><item><title>WikiPage EXAMPLES modified by Xian Su</title><link>https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/</link><description>&lt;pre&gt;--- v2
+++ v3
@@ -3,83 +3,102 @@
 
 This is more of a walkthrough. So it will be long.
 
-1. copy oinkfs.cfg as .oinkfs in your home directory and then modify it
-    cp /path/to/oinkfs.cfg ~/.oinkfs
+    1. copy oinkfs.cfg as .oinkfs in your home directory and then modify it
+        cp /path/to/oinkfs.cfg ~/.oinkfs
 
-This is optional but it'd be handy to have oinkfs and oinklink in your path:
-    sudo ln -s /path/to/oinkfs.py /usr/local/bin/oinkfs
-    sudo ln -s /path/to/oinklink.py /usr/local/bin/oinklink
+    This is optional but it'd be handy to have oinkfs and oinklink in your path:
+        sudo ln -s /path/to/oinkfs.py /usr/local/bin/oinkfs
+        sudo ln -s /path/to/oinklink.py /usr/local/bin/oinklink
 
-2. Setting up your directories, PERM_ROOT and ORIG_ROOT.
-    PERM_ROOT should be structured as PERM_ROOT/$album
-    ORIG_ROOT should be structured as ORIG_ROOT/$whatever/$album
+    2. Setting up your directories, PERM_ROOT and ORIG_ROOT.
+        PERM_ROOT should be structured as PERM_ROOT/$album
+        ORIG_ROOT should be structured as ORIG_ROOT/$whatever/$album
 
-$album can be anything you want but they must match to be considered.
-    Ex:"Artist - Album" or "Artist - Year - Album" or "Album".
+    $album can be anything you want but they must match to be considered.
+        Ex:"Artist - Album" or "Artist - Year - Album" or "Album".
 
-$whatever can be whatever you want, except for "tmp", so that you can have multiple (possibly different) copies of albums in ORIG_ROOT. I have two $whatever directories, one named "what" because I didn't know what to call it and one named "waffles", because I like to eat waffles.
+    $whatever can be whatever you want, except for "tmp", so that you can have multiple 
+    (possibly different) copies of albums in ORIG_ROOT. I have two $whatever directories, 
+    one named "what" because I didn't know what to call it and one named "waffles", because 
+    I like to eat waffles.
 
-Other restrictions for files:
-FLAC files inside PERM_ROOT must start with a 2 digit tracknumber.
-    Ex: "01. Artist - Track.flac" or "01 - Track.flac"
+    Other restrictions for files:
+    FLAC files inside PERM_ROOT must start with a 2 digit tracknumber.
+        Ex: "01. Artist - Track.flac" or "01 - Track.flac"
 
-FLAC files inside ORIG_ROOT must have 2 consecutive digit somewhere in the filename.
-    Ex: "Artist - 01 - Track.flac" or "Weird Track Name 01.flac"
+    FLAC files inside ORIG_ROOT must have 2 consecutive digit somewhere in the filename.
+        Ex: "Artist - 01 - Track.flac" or "Weird Track Name 01.flac"
 
-3. Run oinklink:
-    /path/to/oinklink.py -or- oinklink (if you did the optional step in #1)
+    3. Run oinklink:
+        /path/to/oinklink.py -or- oinklink (if you did the optional step in #1)
 
-    See oinklink.png in the wiki.
+        See oinklink.png in the wiki.
 
-You'll notice in my example that some files are green and some are red. The green ones are matched files and red ones are unmatched. This is correct as I do not keep jpg's or m3u's in my organized directories. The important thing is that 23/23 flacs were matched, saving me 621.68MB.
+    You'll notice in my example that some files are green and some are red. The green ones 
+    are matched files and red ones are unmatched. This is correct as I do not keep jpg's or
+    m3u's in my organized directories. The important thing is that 23/23 flacs were 
+    matched, saving me 621.68MB.
 
-If you look inside LINK_ROOT, you will see the same directory structure as ORIG_ROOT, but the flac files will have accompanying .rdiff files, totalling 48KB.
+    If you look inside LINK_ROOT, you will see the same directory structure as ORIG_ROOT, 
+    but the flac files will have accompanying .rdiff files, totalling 48KB.
 
-    xian@sammael:~&gt; ls -laR /media/raid/links | awk '/rdiff$/{size+=$5} END {print size}'
-    47803
+        ls -laR /media/raid/links | awk '/rdiff$/{size+=$5} END {print size}'
+        47803
 
-4. Run oinkfs:
-    /path/to/oinkfs.py OINKFS_MP -or- oinkfs OINKFS_MP (if you did the optional step in #1)
+    4. Run oinkfs:
+        /path/to/oinkfs.py OINKFS_MP -or- oinkfs OINKFS_MP (if you did the optional step)
 
-    xian@sammael:~/oinkfs&gt; df
-    Filesystem           1K-blocks      Used Available Use% Mounted on
-    /dev/md1              139G   48G   85G  36% /
-    /dev/md6               15T   12T  3.0T  80% /media/raid
-    oinkfs                 15T   12T  3.0T  80% /media/raid/oinkfs
+        xian@sammael:~/oinkfs&gt; df
+        Filesystem           1K-blocks      Used Available Use% Mounted on
+        /dev/md1              139G   48G   85G  36% /
+        /dev/md6               15T   12T  3.0T  80% /media/raid
+        oinkfs                 15T   12T  3.0T  80% /media/raid/oinkfs
 
-If you look inside OINKFS_MP, you will see the files in LINK_ROOT without the .rdiff files. If you try to open the files, it will first patch them into OINKFS_MP/tmp and then open the file descriptor to that file.
+    If you look inside OINKFS_MP, you will see the files in LINK_ROOT without the .rdiff 
+    files. If you try to open the files, it will first patch them into OINKFS_MP/tmp and 
+    then open the file descriptor to that file.
 
-Let's try some md5sum's:
-PERM_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  02. The Shins - Simple Song.flac
-ORIG_ROOT: d5367de8d4ae9f1483eb825520ab7664  02 - Simple Song.flac
-LINK_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  02 - Simple Song.flac
-OINKFS_MP: d5367de8d4ae9f1483eb825520ab7664  02 - Simple Song.flac
+    Let's try some md5sum's:
+        PERM_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  02. The Shins - Simple Song.flac
+        ORIG_ROOT: d5367de8d4ae9f1483eb825520ab7664  02 - Simple Song.flac
+        LINK_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  02 - Simple Song.flac
+        OINKFS_MP: d5367de8d4ae9f1483eb825520ab7664  02 - Simple Song.flac
 
-You can now backup and remove the album in ORIG_ROOT. The only copy on your drive will be the one in PERM_ROOT, the link in LINK_ROOT and the patch file. Because your only copy is now in PERM_ROOT, you must NOT change this file, or you will lose the original file. See the FAQ below for how to modify PERM_ROOT.
+    You can now backup and remove the album in ORIG_ROOT. The only copy on your drive will 
+    be the one in PERM_ROOT, the link in LINK_ROOT and the patch file. Because your only 
+    copy is now in PERM_ROOT, you must NOT change this file, or you will lose the original 
+    file. See the FAQ below for how to modify PERM_ROOT.
 
-If you look inside OINKFS_MP/tmp, you will see 2 files, the song we just md5sum'd and oinkfs.log which if you look inside, you will see:
-2012/11/21 04:23:17 creating ./tmp/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
-You can also delete the files in OINKFS_MP/tmp at anytime because they will be re-created whenever they are opened.
+    If you look inside OINKFS_MP/tmp, you will see 2 files, the song we just md5sum'd and 
+    oinkfs.log which if you look inside, you will see:
+    2012/11/21 04:23:17 creating ./tmp/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
+    You can also delete the files in OINKFS_MP/tmp at anytime because they will be 
+    re-created whenever they are opened.
 
-Q. More FAQs?
-A. Seriously? Sigh...
+    Q. More FAQs?
+    A. Seriously? Sigh...
 
-Q. How do I unmount this shit?
-A. fusermount -u OINKFS_MOUNTPOINT
+    Q. How do I unmount this shit?
+    A. fusermount -u OINKFS_MOUNTPOINT
 
-Q. If I don't set DEL_FILES in .oinkfs, I have to delete files myself?
-A. You can create a cronjob to delete files not access over an hour: find OINKFS_MOUNTPOINT/tmp -amin +60 -exec rm {} \;
-                    or to delete files not accessed for over a week: find OINKFS_MOUNTPOINT/tmp -atime +7 -exec rm {} \;
+    Q. If I don't set DEL_FILES in .oinkfs, I have to delete files myself?
+    A. You can create a cronjob to delete files not access over an hour:
+        find OINKFS_MOUNTPOINT/tmp -amin +60 -exec rm {} \;
+    or to delete files not accessed for over a week:
+        find OINKFS_MOUNTPOINT/tmp -atime +7 -exec rm {} \;
 
-Q. Why are my files suddenly colored white on a blue background?
-A. That's normal. It means that there are multiple entries pointed at the inode.
+    Q. Why are my files suddenly colored white on a blue background?
+    A. That's normal. It means that there are multiple entries pointed at the inode.
 
-Q. I want to modify an album in my PERM_ROOT directory. What do I do?
-A. Just copy album from OINKFS_MP to ORIG_ROOT, delete the album in LINK_ROOT, and then modify the album in PERM_ROOT. Next time oinklink is run, it will relink and repatch the album.
+    Q. I want to modify an album in my PERM_ROOT directory. What do I do?
+    A. Just copy album from OINKFS_MP to ORIG_ROOT, delete the album in LINK_ROOT, and then 
+    modify the album in PERM_ROOT. Next time oinklink is run, it will relink and repatch 
+    the album.
 
-Q. How do I manually create patches?
-A. optional: 1. md5sum ORIG_FILE
-             2. rdiff signature PERM_FILE PERM_FILE.sig
-             3. rdiff delta PERM_FILE.sig ORIG_FILE PERM_FILE.rdiff
-   optional: 4. rdiff patch PERM_FILE PERM_FILE.rdiff | md5sum
-   Check #1 and #4 to see if they match. Place PERM_FILE and PERM_FILE.rdiff in LINK_ROOT and you should now be able to open ORIG_FILE through OINKFS_MP.
+    Q. How do I manually create patches?
+    A. optional: 1. md5sum ORIG_FILE
+                 2. rdiff signature PERM_FILE PERM_FILE.sig
+                 3. rdiff delta PERM_FILE.sig ORIG_FILE PERM_FILE.rdiff
+       optional: 4. rdiff patch PERM_FILE PERM_FILE.rdiff | md5sum
+    Check #1 and #4 to see if they match. Place PERM_FILE and PERM_FILE.rdiff in LINK_ROOT 
+    and you should now be able to open ORIG_FILE through OINKFS_MP.
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Xian Su</dc:creator><pubDate>Wed, 21 Nov 2012 10:02:53 -0000</pubDate><guid>https://sourceforge.net4d9654ad4a96811ccd8d1c8e18c75612962ec83f</guid></item><item><title>WikiPage EXAMPLES modified by Xian Su</title><link>https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/</link><description>&lt;pre&gt;--- v1
+++ v2
@@ -4,60 +4,62 @@
 This is more of a walkthrough. So it will be long.
 
 1. copy oinkfs.cfg as .oinkfs in your home directory and then modify it
-   cp /path/to/oinkfs.cfg ~/.oinkfs
+    cp /path/to/oinkfs.cfg ~/.oinkfs
 
-   This is optional but it'd be handy to have oinkfs and oinklink in your path:
-   sudo ln -s /path/to/oinkfs.py /usr/local/bin/oinkfs
-   sudo ln -s /path/to/oinklink.py /usr/local/bin/oinklink
+This is optional but it'd be handy to have oinkfs and oinklink in your path:
+    sudo ln -s /path/to/oinkfs.py /usr/local/bin/oinkfs
+    sudo ln -s /path/to/oinklink.py /usr/local/bin/oinklink
 
 2. Setting up your directories, PERM_ROOT and ORIG_ROOT.
-   PERM_ROOT should be structured as PERM_ROOT/$album
-   ORIG_ROOT should be structured as ORIG_ROOT/$whatever/$album
+    PERM_ROOT should be structured as PERM_ROOT/$album
+    ORIG_ROOT should be structured as ORIG_ROOT/$whatever/$album
 
-   $album can be anything you want but they must match to be considered. For example, it can be "Artist - Album" or "Artist - Year - Album" or "Album".
-   $whatever can be whatever you want, except for "tmp", so that you can have multiple (possibly different) copies of albums in ORIG_ROOT. I have two $whatever
-   directories, one named "what" because I didn't know what to call it and one named "waffles", because I like to eat waffles.
+$album can be anything you want but they must match to be considered.
+    Ex:"Artist - Album" or "Artist - Year - Album" or "Album".
 
-   Other restrictions for files:
-   FLAC files inside PERM_ROOT must start with a 2 digit tracknumber. Ex: "01. Artist - Track.flac" or "01 - Track.flac"
-   FLAC files inside ORIG_ROOT must have 2 consecutive digit somewhere in the filename. Ex: "Artist - 01 - Track.flac" or "Weird Track Name 01.flac"
+$whatever can be whatever you want, except for "tmp", so that you can have multiple (possibly different) copies of albums in ORIG_ROOT. I have two $whatever directories, one named "what" because I didn't know what to call it and one named "waffles", because I like to eat waffles.
+
+Other restrictions for files:
+FLAC files inside PERM_ROOT must start with a 2 digit tracknumber.
+    Ex: "01. Artist - Track.flac" or "01 - Track.flac"
+
+FLAC files inside ORIG_ROOT must have 2 consecutive digit somewhere in the filename.
+    Ex: "Artist - 01 - Track.flac" or "Weird Track Name 01.flac"
 
 3. Run oinklink:
-   /path/to/oinklink.py -or- oinklink (if you did the optional step in #1)
+    /path/to/oinklink.py -or- oinklink (if you did the optional step in #1)
 
-   See oinklink.png in the wiki.
+    See oinklink.png in the wiki.
 
-   You'll notice in my example that some files are green and some are red. The green ones are matched files and red ones are unmatched. This is correct as I do
-   not keep jpg's or m3u's in my organized directories. The important thing is that 23/23 flacs were matched, saving me 621.68MB.
+You'll notice in my example that some files are green and some are red. The green ones are matched files and red ones are unmatched. This is correct as I do not keep jpg's or m3u's in my organized directories. The important thing is that 23/23 flacs were matched, saving me 621.68MB.
 
-   If you look inside LINK_ROOT, you will see the same directory structure as ORIG_ROOT, but the flac files will have accompanying .rdiff files, totalling 48KB.
-   xian@sammael:~&gt; ls -laR /media/raid/links | awk '/rdiff$/{size+=$5} END {print size}'
-   47803
+If you look inside LINK_ROOT, you will see the same directory structure as ORIG_ROOT, but the flac files will have accompanying .rdiff files, totalling 48KB.
+
+    xian@sammael:~&gt; ls -laR /media/raid/links | awk '/rdiff$/{size+=$5} END {print size}'
+    47803
 
 4. Run oinkfs:
-   /path/to/oinkfs.py OINKFS_MP -or- oinkfs OINKFS_MP (if you did the optional step in #1)
+    /path/to/oinkfs.py OINKFS_MP -or- oinkfs OINKFS_MP (if you did the optional step in #1)
 
-   xian@sammael:~/oinkfs&gt; df
-   Filesystem           1K-blocks      Used Available Use% Mounted on
-   /dev/md1              139G   48G   85G  36% /
-   /dev/md6               15T   12T  3.0T  80% /media/raid
-   oinkfs                 15T   12T  3.0T  80% /media/raid/oinkfs
+    xian@sammael:~/oinkfs&gt; df
+    Filesystem           1K-blocks      Used Available Use% Mounted on
+    /dev/md1              139G   48G   85G  36% /
+    /dev/md6               15T   12T  3.0T  80% /media/raid
+    oinkfs                 15T   12T  3.0T  80% /media/raid/oinkfs
 
-   If you look inside OINKFS_MP, you will see the files in LINK_ROOT without the .rdiff files. If you try to open the files, it will first patch them into
-   OINKFS_MP/tmp and then open the file descriptor to that file.
+If you look inside OINKFS_MP, you will see the files in LINK_ROOT without the .rdiff files. If you try to open the files, it will first patch them into OINKFS_MP/tmp and then open the file descriptor to that file.
 
-   Let's try some md5sum's:
-   PERM_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  /media/raid/music/The Shins - Port of Morrow/02. The Shins - Simple Song.flac
-   ORIG_ROOT: d5367de8d4ae9f1483eb825520ab7664  /media/raid/oink/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
-   LINK_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  /media/raid/links/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
-   OINKFS_MP: d5367de8d4ae9f1483eb825520ab7664  /media/raid/oinkfs/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
+Let's try some md5sum's:
+PERM_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  02. The Shins - Simple Song.flac
+ORIG_ROOT: d5367de8d4ae9f1483eb825520ab7664  02 - Simple Song.flac
+LINK_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  02 - Simple Song.flac
+OINKFS_MP: d5367de8d4ae9f1483eb825520ab7664  02 - Simple Song.flac
 
-   You can now backup and remove the album in ORIG_ROOT. The only copy on your drive will be the one in PERM_ROOT, the link in LINK_ROOT and the patch file.
-   Because your only copy is now in PERM_ROOT, you must NOT change this file, or you will lose the original file. See the FAQ below for how to modify PERM_ROOT.
+You can now backup and remove the album in ORIG_ROOT. The only copy on your drive will be the one in PERM_ROOT, the link in LINK_ROOT and the patch file. Because your only copy is now in PERM_ROOT, you must NOT change this file, or you will lose the original file. See the FAQ below for how to modify PERM_ROOT.
 
-   If you look inside OINKFS_MP/tmp, you will see 2 files, the song we just md5sum'd and oinkfs.log which if you look inside, you will see:
-   2012/11/21 04:23:17 creating ./tmp/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
-   You can also delete the files in OINKFS_MP/tmp at anytime because they will be re-created whenever they are opened.
+If you look inside OINKFS_MP/tmp, you will see 2 files, the song we just md5sum'd and oinkfs.log which if you look inside, you will see:
+2012/11/21 04:23:17 creating ./tmp/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
+You can also delete the files in OINKFS_MP/tmp at anytime because they will be re-created whenever they are opened.
 
 Q. More FAQs?
 A. Seriously? Sigh...
@@ -73,8 +75,7 @@
 A. That's normal. It means that there are multiple entries pointed at the inode.
 
 Q. I want to modify an album in my PERM_ROOT directory. What do I do?
-A. Just copy album from OINKFS_MP to ORIG_ROOT, delete the album in LINK_ROOT, and then modify the album in PERM_ROOT. Next time oinklink is run, it will relink
-   and repatch the album.
+A. Just copy album from OINKFS_MP to ORIG_ROOT, delete the album in LINK_ROOT, and then modify the album in PERM_ROOT. Next time oinklink is run, it will relink and repatch the album.
 
 Q. How do I manually create patches?
 A. optional: 1. md5sum ORIG_FILE
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Xian Su</dc:creator><pubDate>Wed, 21 Nov 2012 09:48:49 -0000</pubDate><guid>https://sourceforge.netb7808f9c784c6509f777ba2fcc2c8217e21f329a</guid></item><item><title>WikiPage EXAMPLES modified by Xian Su</title><link>https://sourceforge.net/p/oinkfs/wiki/EXAMPLES/</link><description>EXAMPLES
========

This is more of a walkthrough. So it will be long.

1. copy oinkfs.cfg as .oinkfs in your home directory and then modify it
   cp /path/to/oinkfs.cfg ~/.oinkfs

   This is optional but it'd be handy to have oinkfs and oinklink in your path:
   sudo ln -s /path/to/oinkfs.py /usr/local/bin/oinkfs
   sudo ln -s /path/to/oinklink.py /usr/local/bin/oinklink

2. Setting up your directories, PERM_ROOT and ORIG_ROOT.
   PERM_ROOT should be structured as PERM_ROOT/$album
   ORIG_ROOT should be structured as ORIG_ROOT/$whatever/$album

   $album can be anything you want but they must match to be considered. For example, it can be "Artist - Album" or "Artist - Year - Album" or "Album".
   $whatever can be whatever you want, except for "tmp", so that you can have multiple (possibly different) copies of albums in ORIG_ROOT. I have two $whatever
   directories, one named "what" because I didn't know what to call it and one named "waffles", because I like to eat waffles.

   Other restrictions for files:
   FLAC files inside PERM_ROOT must start with a 2 digit tracknumber. Ex: "01. Artist - Track.flac" or "01 - Track.flac"
   FLAC files inside ORIG_ROOT must have 2 consecutive digit somewhere in the filename. Ex: "Artist - 01 - Track.flac" or "Weird Track Name 01.flac"

3. Run oinklink:
   /path/to/oinklink.py -or- oinklink (if you did the optional step in #1)

   See oinklink.png in the wiki.

   You'll notice in my example that some files are green and some are red. The green ones are matched files and red ones are unmatched. This is correct as I do
   not keep jpg's or m3u's in my organized directories. The important thing is that 23/23 flacs were matched, saving me 621.68MB.

   If you look inside LINK_ROOT, you will see the same directory structure as ORIG_ROOT, but the flac files will have accompanying .rdiff files, totalling 48KB.
   xian@sammael:~&gt; ls -laR /media/raid/links | awk '/rdiff$/{size+=$5} END {print size}'
   47803

4. Run oinkfs:
   /path/to/oinkfs.py OINKFS_MP -or- oinkfs OINKFS_MP (if you did the optional step in #1)

   xian@sammael:~/oinkfs&gt; df
   Filesystem           1K-blocks      Used Available Use% Mounted on
   /dev/md1              139G   48G   85G  36% /
   /dev/md6               15T   12T  3.0T  80% /media/raid
   oinkfs                 15T   12T  3.0T  80% /media/raid/oinkfs

   If you look inside OINKFS_MP, you will see the files in LINK_ROOT without the .rdiff files. If you try to open the files, it will first patch them into
   OINKFS_MP/tmp and then open the file descriptor to that file.

   Let's try some md5sum's:
   PERM_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  /media/raid/music/The Shins - Port of Morrow/02. The Shins - Simple Song.flac
   ORIG_ROOT: d5367de8d4ae9f1483eb825520ab7664  /media/raid/oink/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
   LINK_ROOT: e5f9e2e4cb86f380856fe0fdc50104df  /media/raid/links/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
   OINKFS_MP: d5367de8d4ae9f1483eb825520ab7664  /media/raid/oinkfs/waffles/The Shins - Port of Morrow/02 - Simple Song.flac

   You can now backup and remove the album in ORIG_ROOT. The only copy on your drive will be the one in PERM_ROOT, the link in LINK_ROOT and the patch file.
   Because your only copy is now in PERM_ROOT, you must NOT change this file, or you will lose the original file. See the FAQ below for how to modify PERM_ROOT.

   If you look inside OINKFS_MP/tmp, you will see 2 files, the song we just md5sum'd and oinkfs.log which if you look inside, you will see:
   2012/11/21 04:23:17 creating ./tmp/waffles/The Shins - Port of Morrow/02 - Simple Song.flac
   You can also delete the files in OINKFS_MP/tmp at anytime because they will be re-created whenever they are opened.

Q. More FAQs?
A. Seriously? Sigh...

Q. How do I unmount this shit?
A. fusermount -u OINKFS_MOUNTPOINT

Q. If I don't set DEL_FILES in .oinkfs, I have to delete files myself?
A. You can create a cronjob to delete files not access over an hour: find OINKFS_MOUNTPOINT/tmp -amin +60 -exec rm {} \;
                    or to delete files not accessed for over a week: find OINKFS_MOUNTPOINT/tmp -atime +7 -exec rm {} \;

Q. Why are my files suddenly colored white on a blue background?
A. That's normal. It means that there are multiple entries pointed at the inode.

Q. I want to modify an album in my PERM_ROOT directory. What do I do?
A. Just copy album from OINKFS_MP to ORIG_ROOT, delete the album in LINK_ROOT, and then modify the album in PERM_ROOT. Next time oinklink is run, it will relink
   and repatch the album.

Q. How do I manually create patches?
A. optional: 1. md5sum ORIG_FILE
             2. rdiff signature PERM_FILE PERM_FILE.sig
             3. rdiff delta PERM_FILE.sig ORIG_FILE PERM_FILE.rdiff
   optional: 4. rdiff patch PERM_FILE PERM_FILE.rdiff | md5sum
   Check #1 and #4 to see if they match. Place PERM_FILE and PERM_FILE.rdiff in LINK_ROOT and you should now be able to open ORIG_FILE through OINKFS_MP.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Xian Su</dc:creator><pubDate>Wed, 21 Nov 2012 09:42:10 -0000</pubDate><guid>https://sourceforge.net22c58ad9d13480630cbfa962d1c2e556d17ccdbb</guid></item></channel></rss>