9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Plan 9 file server w/ indexed dirs and logging
Date: Wed, 15 Oct 1997 18:41:10 -0500	[thread overview]
Message-ID: <19971015234110.84EXwotg5bxSqkqPA6EJHdLKQ9KDbvrsaQtMZN-Wy2s@z> (raw)

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




             reply	other threads:[~1997-10-15 23:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-15 23:41 G.David [this message]
1997-10-17 21:09 G.David
1997-10-20 22:00 G.David

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19971015234110.84EXwotg5bxSqkqPA6EJHdLKQ9KDbvrsaQtMZN-Wy2s@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).