head	1.24;
access;
symbols
	UNIONFS-1_4:1.24
	LKML-branch:1.24.0.4
	LKML:1.24
	UNIONFS-1_3-branch:1.24.0.2
	UNIONFS-1_3:1.24
	UNIONFS-1_2:1.23.4.1
	UNIONFS-1_2-branch:1.23.0.4
	UNIONFS-1_2-branchpoint:1.23
	UNIONFS_branchman:1.23
	branchman:1.23.0.2
	UNIONFS-1_1_4:1.22
	UNIONFS-1_1-patches:1.22.0.4
	UNIONFS-1_1_3:1.22
	crc-submitted-to-ols2006:1.22
	remount:1.22.0.2
	UNIONFS-1_1_2:1.21
	BEFORE_MOUNTPOINT_CROSSING:1.20
	UNIONFS-1_1_1:1.20
	UNIONFS_PRE_1_1_1:1.20
	UNIONFS-1_1:1.20
	UNIONFS_PRE_1_1:1.20.0.2
	UNIONFS-1_0_14:1.20
	UNIONFS_PRE_DENTRY_LOCKING:1.20
	UNIONFS-1_0_13:1.19
	submitted-to-tos-2005:1.18
	UNIONFS-1_0_12:1.18
	UNIONFS-1_0_11:1.16
	UNIONFS-1_0_10:1.16
	UNIONFS-1_0_9:1.14
	UNIONFS-1_0_6:1.11
	UNIONFS-1_0_4:1.10
	UNIONFS-1_0_3:1.8
	SUBMITTED_TO_USENIX_2005:1.5
	UNIONFS-1_0:1.4
	before-new-rename:1.1
	before_applying_linux_coding_style:1.1
	copied-to-replicfs-branch-on-march-17-2004:1.1
	PRE_SNAPSHOT:1.1
	SUBMITTED_TO_USENIX_2004:1.1
	SUBMITTED_TO_FAST_2004:1.1;
locks; strict;
comment	@# @;


1.24
date	2006.06.09.20.53.05;	author jsipek;	state Exp;
branches
	1.24.4.1;
next	1.23;

1.23
date	2006.04.15.02.59.50;	author jsipek;	state Exp;
branches
	1.23.4.1;
next	1.22;

1.22
date	2006.02.05.04.01.35;	author jsipek;	state Exp;
branches;
next	1.21;

1.21
date	2006.01.03.01.15.56;	author jsipek;	state Exp;
branches;
next	1.20;

1.20
date	2005.08.09.17.12.03;	author cwright;	state Exp;
branches;
next	1.19;

1.19
date	2005.07.20.13.02.52;	author cwright;	state Exp;
branches;
next	1.18;

1.18
date	2005.04.18.13.16.42;	author cwright;	state Exp;
branches;
next	1.17;

1.17
date	2005.04.11.23.39.16;	author dquigley;	state Exp;
branches;
next	1.16;

1.16
date	2005.03.21.15.32.34;	author cwright;	state Exp;
branches;
next	1.15;

1.15
date	2005.02.22.14.49.42;	author cwright;	state Exp;
branches;
next	1.14;

1.14
date	2005.01.13.14.33.54;	author cwright;	state Exp;
branches;
next	1.13;

1.13
date	2005.01.10.14.57.38;	author cwright;	state Exp;
branches;
next	1.12;

1.12
date	2005.01.09.22.03.13;	author cwright;	state Exp;
branches;
next	1.11;

1.11
date	2004.12.30.19.44.51;	author cwright;	state Exp;
branches;
next	1.10;

1.10
date	2004.12.06.19.16.45;	author cwright;	state Exp;
branches;
next	1.9;

1.9
date	2004.11.10.18.53.32;	author cwright;	state Exp;
branches;
next	1.8;

1.8
date	2004.11.10.14.38.03;	author cwright;	state Exp;
branches;
next	1.7;

1.7
date	2004.11.10.00.34.19;	author ezk;	state Exp;
branches;
next	1.6;

1.6
date	2004.11.10.00.28.16;	author ezk;	state Exp;
branches;
next	1.5;

1.5
date	2004.09.23.17.47.01;	author ezk;	state Exp;
branches;
next	1.4;

1.4
date	2004.08.20.14.03.01;	author cwright;	state Exp;
branches;
next	1.3;

1.3
date	2004.08.20.13.52.23;	author cwright;	state Exp;
branches;
next	1.2;

1.2
date	2004.08.20.13.29.46;	author cwright;	state Exp;
branches;
next	1.1;

1.1
date	2003.05.27.23.15.29;	author puja;	state Exp;
branches;
next	;

1.23.4.1
date	2006.06.09.07.09.14;	author jsipek;	state Exp;
branches;
next	;

1.24.4.1
date	2006.08.02.21.23.09;	author jsipek;	state dead;
branches;
next	;


desc
@@


1.24
log
@* Makefile: Up the version number

* README, NEWS: Sync with the 1.2 branch

* Makefile, Makefile.kernel, unionfs.h: Define supported version in
the Makefile; added kvers make target to display the supported
kernel version

* docs/OO-INDEX, docs/versions.txt: Document describing the new
versioning scheme
@
text
@Copyright (c) 2003-2006 Erez Zadok
Copyright (c) 2003-2006 Charles P. Wright
Copyright (c) 2005-2006 Josef Sipek
Copyright (c) 2005      Arun M. Krishnakumar
Copyright (c) 2005-2006 David P. Quigley
Copyright (c) 2003-2004 Mohammad Nayyer Zubair
Copyright (c) 2003      Puja Gupta
Copyright (c) 2003      Harikesavan Krishnan
Copyright (c) 2003-2006 Stony Brook University
Copyright (c) 2003-2006 The Research Foundation of State University of New York

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

We're pleased to announce the first release of a unioning file system
for Linux, called Unionfs.  To download software and documentation,
see

	http://www.fsl.cs.sunysb.edu/project-unionfs.html

Unionfs is a stackable unification file system, which can appear to merge
the contents of several directories (branches), while keeping their physical
content separate.  Unionfs is useful for unified source tree management,
merged contents of split CD-ROM, merged separate software package
directories, data grids, and more.  Unionfs allows any mix of read-only and
read-write branches, as well as insertion and deletion of branches anywhere
in the fan-out.  To maintain Unix semantics, Unionfs handles elimination of
duplicates, partial-error conditions, and more.  This release also includes
additional preliminary features that were specifically designed for security
applications, such as snapshotting and sandboxing.

This Unionfs release supports only one 2.6 kernel version (run 'make kvers'
to find out which).  For older kernels look into Unionfs version 1.0.x and
1.1.x.  For detailed information about the new Unionfs versioning scheme,
look at docs/versions.txt.  You also need to have the development headers
for e2fsprogs installed.

Unionfs is released under the GPL (see the COPYING file in the distribution
for details).

For more information on using Unionfs, download the tarball and see the
following man pages:

- unionfs.4:  Describes how to mount unionfs

- unionctl.8: Describes how to control an already mounted Union

For more information about Unionfs internals (which we think are really cool
:-), see the following technical report at the above Web site:

  C. P. Wright, J. Dave, P. Gupta, H. Krishnan, E. Zadok, and M. Zubair
  "Versatility and Unix Semantics in a Fan-Out Unification File System"
  Technical Report FSL-04-01b, October 2004
  Computer Science Department, Stony Brook University
  http://www.fsl.cs.sunysb.edu/docs/unionfs-tr/unionfs.pdf

In addition, you can find an article in Linux Journal (December 2004 issue)
titled "Unionfs: Bringing File Systems Together."  It is available online at
http://www.linuxjournal.com/article/7714.

See the INSTALL file for instructions on building Unionfs, iteractions with
kernel features, and known bugs and limitations.

To report bugs, please email them to the "unionfs@@filesystems.org" list (see
www.filesystems.org), or submit them via Bugzilla to
https://bugzilla.filesystems.org/.  But reports with fixes are most welcome.

Enjoy,
Erez and Charles (on behalf of the Unionfs team)

##############################################################################
## For Emacs:
# Local variables:
# fill-column: 70
# End:
##############################################################################
@


1.24.4.1
log
@* AUTHORS, BUGS, COPYING, INSTALL, Makefile, Lindent, Makefile.kernel,
NEWS, README, announce-email.txt, commit, doit.sh, patch-kernel.sh,
undoit.sh: (lkml branch) Removed some unneeded files - trying to make
it compile as a part of the kernel tree..
@
text
@@


1.23
log
@* BUGS, man/unionfs.4: Added warning of dire consequences (Bug #256)

* README: Mention latest 2.6 kernel only
@
text
@d12 10
a21 11
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
d29 9
a37 10
Unionfs is a stackable unification file system, which can appear to
merge the contents of several directories (branches), while keeping
their physical content separate.  Unionfs is useful for unified source
tree management, merged contents of split CD-ROM, merged separate
software package directories, data grids, and more.  Unionfs allows
any mix of read-only and read-write branches, as well as insertion and
deletion of branches anywhere in the fan-out.  To maintain Unix
semantics, Unionfs handles elimination of duplicates, partial-error
conditions, and more.  This release also includes additional
preliminary features that were specifically designed for security
d40 5
a44 3
This Unionfs release supports latests 2.6 kernels only.  For older
kernels look into Unionfs version 1.0.x and 1.1.x.  You also need to
have the development headers for e2fsprogs installed.
d46 2
a47 2
Unionfs is released under the GPL (see the COPYING file in the
distribution for details).
d49 2
a50 2
For more information on using Unionfs, download the tarball and see
the following man pages:
d56 2
a57 3
For more information about Unionfs internals (which we think are
really cool :-), see the following technical report at the above Web
site:
d65 3
a67 3
In addition, you can find an article in Linux Journal (December 2004
issue) titled "Unionfs: Bringing File Systems Together."  It is available
online at http://www.linuxjournal.com/article/7714.
d72 3
a74 4
To report bugs, please email them to the "fistgen@@filesystems.org"
list (see www.filesystems.org), or submit them via Bugzilla to
https://bugzilla.filesystems.org/.  But reports with fixes are most
welcome.
@


1.23.4.1
log
@* Makefile, NEWS, README: Version 1.2

* README: Formating fixes

* Makefile, unionfs.h: Define supported version in the Makefile;
added kvers make target to display the supported kernel version

* docs/00-INDEX, docs/versions.txt: Document describing new
versioning scheme
@
text
@d12 11
a22 10
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
d30 10
a39 9
Unionfs is a stackable unification file system, which can appear to merge
the contents of several directories (branches), while keeping their physical
content separate.  Unionfs is useful for unified source tree management,
merged contents of split CD-ROM, merged separate software package
directories, data grids, and more.  Unionfs allows any mix of read-only and
read-write branches, as well as insertion and deletion of branches anywhere
in the fan-out.  To maintain Unix semantics, Unionfs handles elimination of
duplicates, partial-error conditions, and more.  This release also includes
additional preliminary features that were specifically designed for security
d42 3
a44 5
This Unionfs release supports only one 2.6 kernel version (run 'make kvers'
to find out which).  For older kernels look into Unionfs version 1.0.x and
1.1.x.  For detailed information about the new Unionfs versioning scheme,
look at docs/versions.txt.  You also need to have the development headers
for e2fsprogs installed.
d46 2
a47 2
Unionfs is released under the GPL (see the COPYING file in the distribution
for details).
d49 2
a50 2
For more information on using Unionfs, download the tarball and see the
following man pages:
d56 3
a58 2
For more information about Unionfs internals (which we think are really cool
:-), see the following technical report at the above Web site:
d66 3
a68 3
In addition, you can find an article in Linux Journal (December 2004 issue)
titled "Unionfs: Bringing File Systems Together."  It is available online at
http://www.linuxjournal.com/article/7714.
d73 4
a76 3
To report bugs, please email them to the "unionfs@@filesystems.org" list (see
www.filesystems.org), or submit them via Bugzilla to
https://bugzilla.filesystems.org/.  But reports with fixes are most welcome.
@


1.22
log
@* README: Remove reference to 2.4 as we don't support it anymore
@
text
@d42 3
a44 3
This Unionfs release has been tested with recent 2.6 kernels.  For
2.6 kernels, the minimum requirement is 2.6.9.  You also need to have
the development headers for e2fsprogs installed.
@


1.21
log
@* ALL: Copyright year updated

* man/*: Date updated

* misc/split-views-2.4.26.patch: removed because 2.4 is not supported
@
text
@d42 3
a44 4
This Unionfs release has been tested with recent 2.4 and 2.6 kernels.
For the 2.4 kernels, the minimum requirement is 2.4.20.  For 2.6
kernels, the minimum requirement is 2.6.11.  You also need to have the
development headers for e2fsprogs installed.
@


1.20
log
@* Some AMD64 fixes.
* vprintk wrapper for 2.4.
@
text
@d1 10
a10 4
Copyright (c) 2003-2005 Erez Zadok <ezk@@cs.sunysb.edu>
Copyright (c) 2003-2005 Charles P. Wright
Copyright (c) 2003-2005 Stony Brook University
Copyright (c) 2003-2005 The Research Foundation of State University of New York
@


1.19
log
@2005-07-20  Charles P. Wright <cwright@@fsl.cs.sunysb.edu>

	* Fix things so that we compile on 2.4 again, and use the
	older form of ioctl for kernels less than 2.6.11.

	* ChangeLog: 80 character entries.
@
text
@d38 2
a39 1
kernels, the minimum requirement is 2.6.11.
@


1.18
log
@* file.c: Delay copyup of read-write files located on read-only
branches, until an operation will actually write to them (BUG 225).

* INSTALL: Cleanup kernel instructions a bit.
@
text
@d38 1
a38 1
kernels, the minimum requirement is 2.6.9.
@


1.17
log
@* copyup.c : changed comparison from > to >= to be compatable with 2.6.0
* fist.h : same as above
* unionfs.h : same as above
* rdstate.c : same as above
* main.c : same as above
* inode.c : same as above
* super.c : same as above
* xattr.c : sme as above
@
text
@a0 4
***********************************************************************
* Note: Exporting Unionfs over NFS works again.                       *
***********************************************************************

@


1.16
log
@* Add big warnings that NFS exports won't work in 1.0.10.
@
text
@d2 1
a2 1
* Note: Exporting Unionfs over NFS does not work in this release.     *
@


1.15
log
@* README: Article URL.
@
text
@d1 4
@


1.14
log
@* Split README into INSTALL as well.

* Makefile: Spit out a message saying to read install.

* Don't build xattr functions w/o -DUNIONFS_XATTR
@
text
@d61 2
a62 1
issue) titled "Unionfs: Bringing File Systems Together."
@


1.13
log
@* README updates.
@
text
@d63 2
a64 30
To build Unionfs, there are two main components:

- unionfs.o: the kernel module

- unionctl: a user utility which allows you to add and remove branches

You should be able to just type "make" and Unionfs will build itself.
The Makefile will look for your running kernel sources in
/lib/modules/`uname -r`/build/include.  If your kernel sources are
located in a different directory, create a "fistdev.mk" file along the
lines of: TOPINC=-I/path/to/my/kernel/sources/linux-2.4.xx/include

There are two Makefile options related to extended attribute support,
which is turned off by default.  You should define UNIONFS_XATTR to turn
it on.  Vanilla kernels should work automatically, but if you (or your
vendor) has applied the ACL/EA patches you might need to define
FIST_SETXATTR_CONSTVOID to correct the setxattr operation's function
prototype.

Using fistdev.mk, you can also turn off the debugging print system,
which adds to the modules code size significantly.  Just add
"EXTRACFLAGS=-DNODEBUG" to fistdev.mk.

The doit.sh script included in the distribution will mount unionfs
with two branches (/branch0 and /branch1) by default.  You can use it
as an example or edit to your tastes.

To install unionfs run "make install".  This copies unionfs.o into
/lib/modules/`uname -r`/kernel/fs/; copies the utilities into
/usr/local/sbin; and copies man pages into /usr/local/man;
@


1.12
log
@* unionfs.h: Warn when compiling on unsupported kernels.
* super.c: Compile fix for 2.6.8.
* Makefile: Include ChangeLog in the release.
@
text
@d82 4
@


1.11
log
@* *.[ch]: Update year.
@
text
@d36 3
a38 4
This Unionfs release has been tested with recent 2.4 kernels.  If you
are using anything less than 2.4.20, your mileage may vary.  We
currently have no plans to port Unionfs to 2.6, but that may change if
there is sufficient interest.
@


1.10
log
@* README, Makefile, inode.c: Turn off extended attributes, unless
the user specifically turns them back on by defining UNIONFS_XATTR.
This prevents us from getting various compile errors depending on
vendor-specific patches.
@
text
@d1 4
a4 4
Copyright (c) 2003-2004 Erez Zadok <ezk@@cs.sunysb.edu>
Copyright (c) 2003-2004 Charles P. Wright
Copyright (c) 2003-2004 Stony Brook University
Copyright (c) 2003-2004 The Research Foundation of State University of New York
@


1.9
log
@2.6 note
@
text
@d76 7
@


1.8
log
@* README: Added warning that anything less than 2.4.20 is unsupported.
* namei.c: Removed inode_dir_notify calls when we are on less than
2.4.20, because the symbol is not exported.
* Fixed lots of bad casts from pointer to int in printks.
* main.c (unionfs_parse_options): Fix for badly ordered variables.
@
text
@d37 6
a42 3
are using anything less than 2.4.20, your mileage may vary.  Unionfs is
released under the GPL (see the COPYING file in the distribution for
details).
@


1.7
log
@* README (site): fix typo. missing "`".

* Makefile (clean): remove tarball.
@
text
@d36 2
a37 1
This Unionfs release has been tested with recent 2.4 kernels.  It is
@


1.6
log
@* released unionfs-1.0.2.

* README: updated.

* released unionfs-1.0.1.


* released unionfs-1.0.
@
text
@d68 1
a68 1
/lib/modules/`uname -r/build/include.  If your kernel sources are
@


1.5
log
@* announce-email.txt: draft announcement email.

* README: revised.
@
text
@d32 3
a34 3
conditions, and more.  There some additional preliminary features in
Unionfs, specifically suitable for security applications, such as
snapshotting and sandboxing.
d47 9
a55 2
For more information about Unionfs internals (which are really cool),
see the following technical report in the above Web site:
d57 2
a58 5
	P. Gupta, H. Krishnan, C. P. Wright, M. Zubair, J. Dave, and
	E. Zadok.  "Versatility and Unix Semantics in a Fan-Out
	Unification File System."  Technical Report FSL-04-01.
	Computer Science Department, Stony Brook University. January
	2004. www.fsl.cs.sunysb.edu/docs/unionfs-tr/unionfs.pdf.
d80 2
a81 2
To report bugs, please email them to the "fistgen" list (see
www.filesystems.org), or file them via Bugzilla in
a86 6

PS. A Linux Journal article on Unionfs should appear later this year
(probably December 2004) contains several usage examples: Charles
P. Wright and Erez Zadok.  "Unionfs: Bringing File Systems Together."
Linux Journal.

@


1.4
log
@* Makefile: install target
@
text
@d2 1
a2 1
Copyright (c) 2003-2004 Charles Wright
d18 53
a70 40
Unionfs is a stackable unification file system, which can appear to merge the
contents of several directories (branches), while keeping their physical
content separate. Unionfs is useful for unified source tree management, merged
contents of split CD-ROM, merged separate software package directories, data
grids, and more. Unionfs allows any mix of read-only and read-write branches,
as well as insertion and deletion of branches anywhere in the fan-out. To
maintain unix semantics, Unionfs handles elimination of duplicates,
partial-error conditions, and more.

For more information on using Unionfs use the following resources:
unionfs/man/unionfs.4	Describes how to mount unionfs
unionfs/man/unionctl.8	Describes how to control an already mounted Union

Our Linux Journal article contains several usage examples:
Charles P. Wright and Erez Zadok.  Unionfs: Bringing File Systems Together.
Linux Journal.  November 2004.

For more information about Unionfs internals (which are really cool):
P. Gupta, H. Krishnan, C. P. Wright, M. Zubair, J. Dave, and E. Zadok.
Versatility and Unix Semantics in a Fan-Out Unification File System.  Technical
Report FSL-04-01.  Computer Science Department, Stony Brook University. January
2004. www.fsl.cs.sunysb.edu/docs/unionfs-tr/unionfs.pdf.
For the latest information Unionfs visit:
http://www.fsl.cs.sunysb.edu/project-unionfs.html

This Unionfs release has been tested with recent 2.4 kernels.

There are two main components:
	unionfs.o (the kernel module)
	unionctl (a user utiltiy which allows you to add and remove branches).

You should be able to just type "make" and Unionfs will build itself.  The
Makefile will look for your running kernel sources in /lib/modules/`uname
-r/build/include, if your kernel sources are located in a different directory
create a "fistdev.mk" file along the lines of:
TOPINC=-I/path/to/my/kernel/sources/linux-2.4.xx/include

The doit.sh script included in the distribution will mount unionfs with two
branches (/branch0 and /branch1) by default.  You can use it as an example or
edit to your tastes.
d73 23
a95 2
/lib/modules/`uname -r`/kernel/fs/; copies the utilities into /usr/local/sbin;
and copies man pages into /usr/local/man;
@


1.3
log
@No debugging by default.
@
text
@d18 8
d27 17
a43 1
Unionfs has been tested with recent 2.4 kernels.
d55 7
a61 14
To install unionfs copy unionfs.o into /lib/modules/`uname -r`/kernel/fs/
and copy unionctl into /usr/local/sbin.

For more information on using Unionfs use the following resources:
unionfs/man/unionfs.4	Describes how to mount unionfs
unionfs/man/unionctl.8	Describes how to control an already mounted Union
Charles P. Wright and Erez Zadok.  Unionfs: Bringing File Systems Together.
Linux Journal.  November 2004.

For more information about Unionfs internals (which are really cool):
P. Gupta, H. Krishnan, C. P. Wright, M. Zubair, J. Dave, and E. Zadok.
Versatility and Unix Semantics in a Fan-Out Unification File System.  Technical
Report FSL-04-01.  Computer Science Department, Stony Brook University. January
2004. www.fsl.cs.sunysb.edu/docs/unionfs-tr/unionfs.pdf.
@


1.2
log
@* main.c (unionfs_hidden_dentry_index): This function is unused now
that Mohammad took it out, so I removed it.
* Removed unnecessary files.
* COPYING: SUNY we can't be blamed for anything notice; and the GPL.
@
text
@d17 28
@


1.1
log
@added: files from cse506 project (spring 2003)
@
text
@d1 4
a4 4
The project report is located in docs/unionfs.doc

Thanks,
Puja, Hari.
d6 11
@

