From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Wed, 15 Oct 1997 18:41:10 -0500
From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Plan 9 file server w/ indexed dirs and logging
Topicbox-Message-UUID: 6899bce8-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19971015234110.84EXwotg5bxSqkqPA6EJHdLKQ9KDbvrsaQtMZN-Wy2s@z>

Hey all!

I STILL haven't heard from anyone about licensing....

But I want to know how the work I've done thus far works,
so if you have a spare PC to use as a Plan9 file server
and want to have a go at it...  This fileserver has indexed
directories and logging.  [It also supports mirrored disks,
sort of.  It works but needs more attention.]  The logging comes
in two versions (compile flag) of full discrete transactions
and fileserver protection.  The one below only provides
fileserver protection.  The other one guarantees the results
of each successful 9P message.  Both are fully compatible with
the current Plan9 9P protocol.

Get ftp://ftp.dbSystems.com/pub/PLAN9/9pcfs.xor

Using the xor program from the updates on plan9.bell-labs.com
do "?.xor 9pcfs.xor /68020/9gnot > 9pcfs".  This is the same way
Bell Labs distributed dns.tar, so if it is good enough for them,
it's good enough for me.  (I had to do this since the file
server is on the CD.  In other words, you have to own the CD
to try this out, sorry.)

Follow the normal directions to get a Plan9 fileserver up, except:

The system will not boot on a config of a previous system
 (To protect *us*.  You will have to tell the system to destroy
 the drive contents, not I.)

The ipauth command is gone. (That is how I got the above.)

The "users default" only creates adm and none, so you must use
 user none on the initial load.

To enable logging on all filesystems, create a filsys called "log".
 (The system will not honor attaches to "log".)

For a fast temporary filesystem create a filsys called "nolog".
 If logging is enabled, "nolog" will be "reammed" on each boot.

The permissions are different on this filesystem as discussed on
 this list.

I think that is all you need to know to get this running.  You
may notice there is an "index" option to check, but it is not
enabled yet.  The idea is to "fix" the indexes.  Since I think
the whole idea of check is silly, (use the log luke), there are
only consistency checks for now.  If you do find yourself wishing
the index rebuild is there, you will have to clri the *parent*
directory and run check free to get to sanity again.

One other thing, I would recommend a small log so the search for
the end doesn't take too long.  Something like pw0.0.0.0.1 (Yeah
I fixed the partition syntax like the man page...)

I would really like to know if you have any problems with this.
Please email any panics and the like.

Have fun?!

David Butler
gdb@dbSystems.com