moved pgfuse from Github to local server

3 files changed, 78 insertions, 3 deletions

diff --git a/content/blog/openbsd-firewall-appliance-intro.md b/content/blog/openbsd-firewall-appliance-intro.md
index 622ded3..c9b73d2 100644
--- a/content/blog/openbsd-firewall-appliance-intro.md
+++ b/content/blog/openbsd-firewall-appliance-intro.md
@@ -205,8 +205,17 @@ I would like to test more things around the following topics:
 
 ## Github
 
-The whole project can be found on Github:
+The whole project can be found here:
 
-http://github.com/andreasbaumann/OpenBSD-firewall
+git://git.andreasbaumann.cc/OpenBSD-firewall.git or
+http://git.andreasbaumann.cc/cgit/OpenBSD-firewall/
 
 Feedback welcome. :-)
+
+## Note on Github
+
+There is a version on https://github.com/Eurospider/OpenBSD-firewall. This
+is the original version and I don't plan to update it anymore.
+Further development happens on my personal repo (as I'm basically the only
+one using it anyway).
+
diff --git a/content/software/_index.md b/content/software/_index.md
index 2777d88..4ae4cb3 100644
--- a/content/software/_index.md
+++ b/content/software/_index.md
@@ -11,7 +11,7 @@ title = "Software"
 
 ## C
 
-* [pguse](https://github.com/andreasbaumann/pgfuse): a
+* [PgFuse](/software/pgfuse): a
   [FUSE](http://fuse.sourceforge.net) filsystem for the
   [PostgreSQL](http://www.postgresql.org/) database.
 * [cssh](http://git.andreasbaumann.cc/cgit/cssh/): a small parallel SSH
diff --git a/content/software/pgfuse.md b/content/software/pgfuse.md
new file mode 100644
index 0000000..3b848bd
--- /dev/null
+++ b/content/software/pgfuse.md
@@ -0,0 +1,66 @@
++++
+title = "PgFuse"
+description = "FUSE filesystem for PostgreSQL"
++++
+
+## Purpose
+
+Store files and their metadata completely in a PostgreSQL database.
+Expose a standard file system with the help of the FUSE API.
+
+## Requirements
+
+- PostgreSQL 8.4 or newer
+- FUSE 2.6 or newer
+
+## History
+
+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 useful. With FUSE this is also rather simple to write.
+
+The reason I wrote one was a project with lots of data on a ReiserFS (at
+least in 2001, this was), which was more or less immutable and should be 
+efficiently stored away (almost in an archive mode). Backup is no issue
+here (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 withs files/dirs as the only
+available model.
+ 
+## Other projects
+
+### Pgfs:
+
+Stores a filesystem in Postgres, exposes it as a NFS server, rather old
+and I was unable to find the sources.
+
+### mysqlfs
+
+The blueprint I used and got inspired from. Does exactly the same for
+the MySQL database.
+  
+ Also the block splitting algorithm I used more or less from this project.
+
+###  libsqlfs
+
+The same for storing files in a Sqlite database.
+  
+### curlftpfs
+
+Blueprint for some debugging code.
+
+## References
+
+- http://www.postgresql.org/docs/
+- http://fuse.sourceforge.net/
+
+A Git repository is accessible at 
+**git://git.andreasbaumann.cc/pgfuse.git** 
+(or at http://git.andreasbaumann.cc/cgit/pgfuse/)
+
+In case of questions, if you want to supply a patch or if you
+want to collaborate on the project contact me via email.