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

Subversion Repositories or1k

[/] [or1k/] [trunk/] [linux/] [linux-2.4/] [fs/] [umsdos/] [README-WIP.txt] - Blame information for rev 1765

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 1275 phoenix
Changes by Matija Nalis (mnalis@jagor.srce.hr) on umsdos dentry fixing
2
(started by Peter T. Waltenberg )
3
(Final conversion to dentries Bill Hawes )
4
 
5
There is no warning any more.
6
Both read-only and read-write stuff is fixed, both in
7
msdos-compatibile mode, and in umsdos EMD mode, and it seems stable.
8
 
9
Userland NOTE: new umsdos_progs (umssync, umssetup, udosctl & friends) that
10
will compile and work on 2.2.x+ kernels and glibc based systems, as well as
11
kernel patches and other umsdos related information may be found at
12
http://linux.voyager.hr/umsdos/
13
 
14
Information below is getting outdated slowly -- I'll fix it one day when I
15
get enough time - there are more important things to fix right now.
16
 
17
Legend: those lines marked with '+' on the beggining of line indicates it
18
passed all of my tests, and performed perfect in all of them.
19
 
20
Current status (010125) - UMSDOS 0.86j:
21
 
22
(1) pure MSDOS (no --linux-.--- EMD file):
23
 
24
READ:
25
+ readdir                       - works
26
+ lookup                        - works
27
+ read file                     - works
28
 
29
WRITE:
30
+ creat file                    - works
31
+ unlink file                   - works
32
+ write file                    - works
33
+ rename file (same dir)        - works
34
+ rename file (dif. dir)        - works
35
+ rename dir (same dir)         - works
36
+ rename dir (dif. dir)         - works
37
+ mkdir                         - works
38
+ rmdir                         - works
39
 
40
 
41
(2) umsdos (with --linux-.--- EMD file):
42
 
43
READ:
44
+ readdir                       - works
45
+ lookup                        - works
46
+ permissions/owners stuff      - works
47
+ long file names               - works
48
+ read file                     - works
49
+ switching MSDOS/UMSDOS        - works
50
+ switching UMSDOS/MSDOS        - works
51
- pseudo root things            - works mostly. See notes below.
52
+ resolve symlink               - works
53
+ dereference symlink           - works
54
+ dangling symlink              - works
55
+ hard links                    - works
56
+ special files (block/char devices, FIFOs, sockets...) - works
57
+ various umsdos ioctls         - works
58
 
59
 
60
WRITE:
61
+ create symlink                - works
62
+ create hardlink               - works
63
+ create file                   - works
64
+ create special file           - works
65
+ write to file                 - works
66
+ rename file (same dir)        - works
67
+ rename file (dif. dir)        - works
68
+ rename hardlink (same dir)    - works
69
- rename hardlink (dif. dir)    - works, but see notes below.
70
+ rename symlink (same dir)     - works
71
+ rename symlink (dif. dir)     - works
72
+ rename dir (same dir)         - works
73
+ rename dir (dif. dir)         - works
74
+ unlink file                   - works
75
+ notify_change (chown,perms)   - works
76
+ notify_change for hardlinks   - works
77
+ unlink hardlink               - works
78
+ mkdir                         - works
79
+ rmdir                         - works
80
+ umssyncing (many ioctls)      - works
81
 
82
 
83
- CVF-FAT stuff (compressed DOS filesystem) - there is some support from Frank
84
  Gockel  to use it even under umsdosfs, but I
85
  have no way of testing it -- please let me know if there are problems specific
86
  to umsdos (for instance, it works under msdosfs, but not under umsdosfs).
87
 
88
 
89
Some current notes:
90
 
91
Note: creating and using pseudo-hardlinks is always non-perfect, especially
92
in filesystems that might be externally modified like umsdos. There is
93
example is specs file about it. Specifically, moving directory which
94
contains hardlinks will break them.
95
 
96
Note: (about creating hardlinks in pseudoroot mode) - hardlinks created in
97
pseudoroot mode are now again compatibile with 'normal' hardlinks, and vice
98
versa. Thanks to Sorin Iordachescu  for providing fix.
99
See http://linux.voyager.hr/umsdos/hlbug.html for more info and upgrade
100
procedure if you used broken versions...
101
 
102
------------------------------------------------------------------------------
103
 
104
Some general notes:
105
 
106
Good idea when running development kernels is to have SysRq support compiled
107
in kernel, and use Sync/Emergency-remount-RO if you bump into problems (like
108
not being able to umount(2) umsdosfs, and because of it root partition also,
109
or panics which force you to reboot etc.)
110
 
111
I'm unfortunately somewhat out of time to read linux-kernel@vger, but I do
112
check for messages having "UMSDOS" in the subject, and read them.  I might
113
miss some in all that volume, though.  I should reply to any direct e-mail
114
in few days.  If I don't, probably I never got your message.

powered by: WebSVN 2.1.0

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