Update .gear/rules and README files

.gear/rules

@@ -22,4 +22,5 @@ tar.bz2: sources/2.6.36 name=kernel-source-etercifs-2.6.36-1.65
 tar.bz2: sources/2.6.37 name=kernel-source-etercifs-2.6.37-1.68
 tar.bz2: sources/2.6.38 name=kernel-source-etercifs-2.6.38-1.71
 tar.bz2: sources/2.6.39 name=kernel-source-etercifs-2.6.39-1.71
+tar.bz2: sources/3.0 name=kernel-source-etercifs-3.0-1.74
 tar.bz2: etercifs

etercifs/README

@@ -457,6 +457,10 @@ A partial list of the supported mount options follows:
 		otherwise - read from the server. All written data are stored
 		in the cache, but if the client doesn't have Exclusive Oplock,
 		it writes the data to the server.
+  rwpidforward  Forward pid of a process who opened a file to any read or write
+		operation on that file. This prevent applications like WINE
+		from failing on read and write if we use mandatory brlock style.
+  wine  	Switch on pidforwardio+strictcache+forcemand.
   acl   	Allow setfacl and getfacl to manage posix ACLs if server
 		supports them.  (default)
   noacl 	Do not allow setfacl and getfacl calls on this mount
@@ -704,18 +708,6 @@ the start of smb requests and responses can be enabled via:
 
 	echo 1 > /proc/fs/cifs/traceSMB
 
-Two other experimental features are under development. To test these
-requires enabling CONFIG_CIFS_EXPERIMENTAL
-
-	cifsacl support needed to retrieve approximated mode bits based on
-		the contents on the CIFS ACL.
-
-	lease support: cifs will check the oplock state before calling into
-	the vfs to see if we can grant a lease on a file.
-
-	DNOTIFY fcntl: needed for support of directory change 
-			    notification and perhaps later for file leases)
-
 Per share (per client mount) statistics are available in /proc/fs/cifs/Stats
 if the kernel was configured with cifs statistics enabled.  The statistics
 represent the number of successful (ie non-zero return code from the server)