OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [linux/] [linux-2.4/] [Documentation/] [filesystems/] [ufs.txt] - Blame information for rev 1765

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 1275 phoenix
USING UFS
2
=========
3
 
4
mount -t ufs -o ufstype=type_of_ufs device dir
5
 
6
 
7
UFS OPTIONS
8
===========
9
 
10
ufstype=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 os read-only
19
 
20
        44bsd   used in FreeBSD, NetBSD, OpenBSD
21
                supported os read-write
22
 
23
        sun     used in SunOS (Solaris)
24
                supported as read-write
25
 
26
        sunx86  used in SunOS for Intel (Solarisx86)
27
                supported as read-write
28
 
29
        nextstep
30
                used in NextStep
31
                supported as read-only
32
 
33
        nextstep-cd
34
                used for NextStep CDROMs (block_size == 2048)
35
                supported as read-only
36
 
37
        openstep
38
                used in OpenStep
39
                supported as read-only
40
 
41
 
42
POSSIBLE PROBLEMS
43
=================
44
 
45
There is still bug in reallocation of fragment, in file fs/ufs/balloc.c,
46
line 364. But it seem working on current buffer cache configuration.
47
 
48
 
49
BUG REPORTS
50
===========
51
 
52
Any ufs bug report you can send to daniel.pirkl@email.cz (do not send
53
partition tables bug reports.)

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.