added more stub functions for dir handling

added a write and an internal file buffer structure (PgFuseFile)
started to implement create/open and release

1 files changed, 28 insertions, 0 deletions

diff --git a/README b/README
index aa0bb6a..9e173e7 100644
--- a/README
+++ b/README
@@ -1,3 +1,31 @@
+Motivation
+----------
+
+Yes, I know what happens if you store files in a database (in respect to
+drop of efficiency and incremental backups for instance). :-)
+
+Nevertheless, there are special situations, where a filesystem in a database
+is usefull. With FUSE this is also rather simple to write.
+
+The reason I wrote one was a projects with lots of data on a ReiserFS, which
+was more or less immutable and should be efficiently stored away (almost in
+an archive mode). Backup is no issue there (as the files are more or less
+static after an initial load), but space efficiency is an issue.
+
+Most other projects try to map an existing database structure somehow as
+files. This here should strictly deal with files/dirs as the only model.
+ 
+Other projects
+--------------
+
+Pgfs: store a filesystem in Postgres, expose it as NFS server, rather old
+      and I was unable to find the sources
+
+mysqlfs: the blueprint I used and got inspired from.
+
+References
+----------
+
 http://www.cs.hmc.edu/~geoff/classes/hmc.cs135.201109/homework/fuse/fuse_doc.html
 http://www.postgresql.org/docs/8.3/static/libpq-example.html
 http://www.postgresql.org/docs/8.0/static/libpq-example.html