summaryrefslogblamecommitdiff
path: root/Documentation/filesystems/ufs.txt
blob: 2b5a56a6a5588cd102fcbd57a3b2e8d700489f40 (plain) (tree) 
1da177e4c3f4





























































1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
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.)