* overview2.sgml (ov-hi-files): Remove reference to root directory when

explaining fstab content.  Add paragraph about Extended Attributes.
	Discourage chroot.

winsup/doc/ChangeLog

@@ -1,3 +1,9 @@
+2009-11-18  Corinna Vinschen  <corinna@vinschen.de>
+
+	* overview2.sgml (ov-hi-files): Remove reference to root directory when
+	explaining fstab content.  Add paragraph about Extended Attributes.
+	Discourage chroot.
+
 2009-11-16  Corinna Vinschen  <corinna@vinschen.de>
 
 	* pathnames.sgml (pathnames-specialchars): Fix typos.

winsup/doc/overview2.sgml

@@ -177,9 +177,9 @@ the mount points point to Win32 paths.  An installation with
 <command>setup.exe</command> installs a <filename>fstab</filename> file by
 default, which can easily be changed using the editor of your choice.</para>
 
-<para>In addition to selecting the root partition, the
+<para>The <filename>fstab</filename> file allows mounting arbitrary Win32
-<filename>fstab</filename> file allows mounting arbitrary Win32 paths into
+paths into the POSIX file system space.  A special case is the so-called
-the POSIX file system space.  A special case is the so-called cygdrive prefix.
+cygdrive prefix.
 It's the path under which every available drive in the system is mounted
 under its drive letter.  The default value is <filename>/cygdrive</filename>,
 so you can access the drives as <filename>/cygdrive/c</filename>,
@@ -237,18 +237,23 @@ guaranteed to be unique.  However, we have not found this to be a significant
 problem because of the low probability of generating a duplicate inode number.
 </para>
 
-<para><function>chroot(2)</function> is supported since Cygwin 1.1.3.
+<para>Cygwin 1.7 and later supports Extended Attributes (EAs) via the
-However, chroot is not a concept known by Windows.  This implies some
+linux-specific function calls <function>getxattr</function>,
+<function>setxattr</function>, <function>listxattr</function>, and
+<function>removexattr</function>.  All EAs on Samba or NTFS are treated as
+user EAs, so, if the name of an EA is "foo" from the Windows perspective,
+it's transformed into "user.foo" within Cygwin.  This allows Linux-compatible
+EA operations and keeps tools like <command>attr</command>, or
+<command>setfattr</command> happy.
+</para>
+
+<para><function>chroot</function> is supported since Cygwin 1.1.3.
+However, chroot is not a concept known by Windows.  This implies some serious
 restrictions.  First of all, the <function>chroot</function> call isn't a
 privileged call.  Any user may call it.  Second, the chroot environment
-isn't safe against native windows processes.  If you want to use a
+isn't safe against native windows processes.  Given that, chroot in Cygwin
-chroot environment to, for example, allow anonymous ftp with restricted
+is only a hack which pretends security where there is none.  For that reason
-access, you must make sure care that only native Cygwin applications
+the usage of chroot is discouraged.
-are accessible inside of the chroot environment.  Since those applications
-are only using the Cygwin POSIX API to access the file system their access
-can be restricted as it is intended.  This includes not only POSIX paths but
-Win32 paths containing drive letter and/or backslashes as well as UNC paths
-(<filename>//server/share</filename> or <filename>\\server\share</filename>).
 </para>
 </sect2>