PageRenderTime 20ms CodeModel.GetById 13ms app.highlight 1ms RepoModel.GetById 2ms app.codeStats 0ms

/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
 1USING UFS
 2=========
 3
 4mount -t ufs -o ufstype=type_of_ufs device dir
 5
 6
 7UFS OPTIONS
 8===========
 9
10ufstype=type_of_ufs
11	UFS is a file system widely used in different operating systems.
12	The problem are differences among implementations. Features of
13	some implementations are undocumented, so its hard to recognize
14	type of ufs automatically. That's why user must specify type of 
15	ufs manually by mount option ufstype. Possible values are:
16
17	old	old format of ufs
18		default value, supported as read-only
19
20	44bsd	used in FreeBSD, NetBSD, OpenBSD
21		supported as read-write
22
23	ufs2    used in FreeBSD 5.x
24		supported as read-only
25
26	5xbsd	synonym for ufs2
27
28	sun	used in SunOS (Solaris)
29		supported as read-write
30
31	sunx86	used in SunOS for Intel (Solarisx86)
32		supported as read-write
33
34	hp	used in HP-UX
35		supported as read-only
36
37	nextstep
38		used in NextStep
39		supported as read-only
40
41	nextstep-cd
42		used for NextStep CDROMs (block_size == 2048)
43		supported as read-only
44
45	openstep
46		used in OpenStep
47		supported as read-only
48
49
50POSSIBLE PROBLEMS
51=================
52
53There is still bug in reallocation of fragment, in file fs/ufs/balloc.c, 
54line 364. But it seems working on current buffer cache configuration.
55
56
57BUG REPORTS
58===========
59
60Any ufs bug report you can send to daniel.pirkl@email.cz (do not send 
61partition tables bug reports.)