Documentation: filesystems: Convert ufs.txt to reStructuredText format

This converts the plain text documentation of ufs.txt to
reStructuredText format. Added to documentation build process
and verified with make htmldocs

Signed-off-by: Shobhit Kukreti <shobhitkukreti@gmail.com>
Reviewed-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Shobhit Kukreti
2019-07-10 08:31:23 -07:00
committed by Jonathan Corbet
parent ac841c4e45
commit 34d5f4f269
2 changed files with 23 additions and 14 deletions

View File

@@ -79,6 +79,7 @@ configure specific aspects of kernel behavior to your liking.
binderfs
xfs
jfs
ufs
pm/index
thunderbolt
LSM/index

View File

@@ -0,0 +1,68 @@
=========
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-write
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
-----------------
See next section, if you have any.
Bug Reports
-----------
Any ufs bug report you can send to daniel.pirkl@email.cz or
to dushistov@mail.ru (do not send partition tables bug reports).