head	1.4;
access;
symbols
	UNIONFS-1_4:1.4
	LKML-branch:1.4.0.8
	LKML:1.4
	UNIONFS-1_3-branch:1.4.0.6
	UNIONFS-1_3:1.4
	UNIONFS-1_2:1.4
	UNIONFS-1_2-branch:1.4.0.4
	UNIONFS-1_2-branchpoint:1.4
	UNIONFS_branchman:1.4
	branchman:1.4.0.2
	UNIONFS-1_1_4:1.3
	UNIONFS-1_1-patches:1.3.0.6
	UNIONFS-1_1:1.3.0.4
	UNIONFS-1_1_3:1.3
	crc-submitted-to-ols2006:1.3
	remount:1.3.0.2
	UNIONFS-1_1_2:1.3
	BEFORE_MOUNTPOINT_CROSSING:1.1
	UNIONFS-1_1_1:1.1;
locks; strict;
comment	@# @;


1.4
date	2006.04.15.02.59.50;	author jsipek;	state Exp;
branches
	1.4.8.1;
next	1.3;

1.3
date	2006.01.21.02.58.11;	author jsipek;	state Exp;
branches;
next	1.2;

1.2
date	2006.01.14.01.23.12;	author jsipek;	state Exp;
branches;
next	1.1;

1.1
date	2005.10.19.17.43.16;	author cwright;	state Exp;
branches;
next	;

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


desc
@@


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

* README: Mention latest 2.6 kernel only
@
text
@This file has a list of bugs or misfeatures  with other systems that affect
Unionfs.  To see a somewhat comprehensive list of Unionfs bugs visit
https://bugzilla.filesystems.org

The NFS server returns -EACCES for read-only exports, instead of -EROFS.  This
means we can't reliably detect a read-only NFS export.  If you want to use
copy-on-write with NFS, set the per-branch option `nfsro'.  If this flag
is set, then Unionfs will apply standard Unix permissions to files on this
nfs-mouted branch.

Modifying a Unionfs branch directly, while the union is mounted is currently
unsupported.  Any such change can cause Unionfs to oops, however it could even
RESULT IN DATA LOSS.

The PPC module loading algorithm has an O(N^2) loop, so it takes a while to
load the Unionfs module, because we have lots of symbols.

Older versions of Reiser4 don't work with Unionfs, because they can't handle
seeking through directories properly.
@


1.4.8.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.3
log
@* BUGS, INSTALL, man/unionctl.8, man/unionfs.4: Documentation update

* branchman.c (unionfs_ioctl_addbranch, unionfs_ioctl_rdwrbranch):
Per branch nfsro option

* inode.c (inode_permission): Per branch nfsro option

* main.c (parse_dirs_option, unionfs_parse_options): Per branch nfsro
option

* super.c (unionfs_show_options): Per branch nfsro option

* unionctl.c (__usage, parse_rw, parse_options, dump_branches, main):
Per branch nfsro option

* unionfs.h: Per branch nfsro option
@
text
@d11 4
@


1.2
log
@* BUGS, INSTALL: Removed all references to NFS_SECURITY_HOLE
@
text
@d3 1
a3 1
http://bugzilla.fsl.cs.sunysb.edu.
d7 3
a9 2
copy-on-write with NFS, mount the unionfs with nfsperms=insecure.  If this flag
is set, then Unionfs will apply standard Unix permissions to files on NFS.
@


1.1
log
@* inode.c (inode_permission): If NFS_SECURITY_HOLE is defined
treat -EACCESS as if we should fall back on inode_permission.
@
text
@d7 2
a8 2
copy-on-write with NFS compile with -DNFS_SECURITY_HOLE.  If this flag is set,
then Unionfs will apply standard Unix permissions to files on NFS.
@

