Return-Path: <tibbetts@MIT.EDU>
Received: from fort-point-station.mit.edu by po11.mit.edu (8.9.2/4.7) id WAA26669; Mon, 29 Jul 2002 22:16:25 -0400 (EDT)
Received: from descartes (DESCARTES.MIT.EDU [18.238.2.27])
	by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id WAA06357
	for <sipb-office@mit.edu>; Mon, 29 Jul 2002 22:15:31 -0400 (EDT)
Received: from tibbetts by descartes with local (Exim 3.35 #1 (Debian))
	id 17ZMXr-0007qN-00
	for <sipb-office@mit.edu>; Mon, 29 Jul 2002 22:15:31 -0400
Date: Mon, 29 Jul 2002 22:15:31 -0400
From: Richard Tibbetts <tibbetts@MIT.EDU>
To: sipb-office@mit.edu
Subject: README for /u1 on snorklewacker
Message-ID: <20020730021531.GA29838@mit.edu>
Mail-Followup-To: sipb-office@mit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i


So, snork (the machine sitting next to the office stereo, which
currenly runs xvolume and will soon run -Psipbmp3) now has a big disk
mounted as /u1. I have been asked by a couple of people to clarify and
codify the purpose of this disk. So here is a readme. Its pretty
vague, but hopefully it will mean that everyone is on the same page.

If you feels discussion or further consideration of this document is
meritted, or anything like that, you are welcome to send mail to me
personally. If you think discussion needs to happen in a more public
forum, then sipb-discussion is probably appropriate.

As far as people who want to use the disk: If you can log in, feel
free to read and write to it. Try not to hurt the network. At some
point in the near future the disk may be served via NFS or HTTP or
something else. Anyone who can't log in and wants access can let me
know.

tibbetts

----
/u1/README

The /u1 partition of this machine is for semi-permanent public data
storage by SIPB members and others. It holds 120 gigs. Additional
disks may be added if needed.

Data will not be backed up. Data may be lost at any time for any
reason. Anyone who considers themselves a maintainer of the machine
may delete any amount of data at any time for any reason. They may
also move data around, or anything else they feel like doing, with or
without announcement.

Data is public. The data will be public to the SIPB community, more or
less. Administrators of the machine may put in place any kind of
authentication or access control, for reading or writing, including
none. Access may be given to anyone, with or without announcement.

tibbetts@mit.edu, July 7, 2002
