1 files changed, 61 insertions, 0 deletions

diff --git a/Documentation/filesystems/ufs.txt b/Documentation/filesystems/ufs.txt
new file mode 100644
index 000000000000..2b5a56a6a558
--- /dev/null
+++ b/Documentation/filesystems/ufs.txt
@@ -0,0 +1,61 @@
+USING UFS
+=========
+
+mount -t ufs -o ufstype=type_of_ufs device dir
+
+
+UFS OPTIONS
+===========
+
+ufstype=type_of_ufs
+        UFS is a file system widely used in different operating systems.
+        The problem are differences among implementations. Features of
+        some implementations are undocumented, so its hard to recognize
+        type of ufs automatically. That's why user must specify type of 
+        ufs manually by mount option ufstype. Possible values are:
+
+        old     old format of ufs
+                default value, supported as read-only
+
+        44bsd   used in FreeBSD, NetBSD, OpenBSD
+                supported as read-write
+
+        ufs2    used in FreeBSD 5.x
+                supported as read-only
+
+        5xbsd   synonym for ufs2
+
+        sun     used in SunOS (Solaris)
+                supported as read-write
+
+        sunx86  used in SunOS for Intel (Solarisx86)
+                supported as read-write
+
+        hp      used in HP-UX
+                supported as read-only
+
+        nextstep
+                used in NextStep
+                supported as read-only
+
+        nextstep-cd
+                used for NextStep CDROMs (block_size == 2048)
+                supported as read-only
+
+        openstep
+                used in OpenStep
+                supported as read-only
+
+
+POSSIBLE PROBLEMS
+=================
+
+There is still bug in reallocation of fragment, in file fs/ufs/balloc.c, 
+line 364. But it seems working on current buffer cache configuration.
+
+
+BUG REPORTS
+===========
+
+Any ufs bug report you can send to daniel.pirkl@email.cz (do not send 
+partition tables bug reports.)