/Documentation/filesystems/ufs.txt
https://bitbucket.org/evzijst/gittest · Plain Text · 61 lines · 41 code · 20 blank · 0 comment · 0 complexity · a9d6b5afa54444338d2921de750dd0d8 MD5 · raw file
- 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.)