From: "Matt" <matt@proweb.co.uk>
To: "9fans" <9fans@cse.psu.edu>
Subject: [9fans] logging file changes
Date: Mon, 18 Sep 2000 21:02:39 +0100 [thread overview]
Message-ID: <002b01c021ab$6ba566e0$0301a8c0@freeze> (raw)
Hi,
I'm currently researching some stuff for work.
We're trying to arrange our network.
What we're looking for is a way to keep track of data associated with
specific files that isn't part of the normal stat data
you know the stuff : author, client, date created, a list of who has
modified it, keywords to help find it, QA details etc. etc.
All the ways I've come up with so far rely on a database and somehow
maintaining it
It struck me that 9p would be the ideal solution as all file requests go
through a plan9 file server which can have rules that operate at a higher
level than simple permissions and so can maintain the database itself.
Has anyone already implemented such a system?
The sub-problem of course is that we have mainly Windows clients.
They will be getting file access via SAMBA on to the Unix box which would
then use u9fs to connect to the plan9 box.
Extra overhead I realise but AFAIK there isn't another way to implement this
crazy scheme and that's why I'm writing this.
I want to try and put plan9's case forward.
Can anyone see any holes? (apart from me having to write the file server
part :)
Matt
next reply other threads:[~2000-09-18 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-18 20:02 Matt [this message]
2000-09-19 4:16 Russ Cox
2000-09-19 4:39 ` Lucio De Re
2000-09-19 20:46 ` Matt
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='002b01c021ab$6ba566e0$0301a8c0@freeze' \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/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).