summaryrefslogtreecommitdiffstats
path: root/sys/fs/cd9660/TODO
blob: eb24a2364bd40c5295ebd39268c9c51b95018380 (plain)
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
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
#	$FreeBSD$

 1) should understand "older", original High Sierra ("CDROM001") type

   Not yet. ( I don't have this technical information, yet. )
   Done. (16-Jan-95, Joerg Wunsch joerg@freebsd.org)


 2) should understand Rock Ridge

   Yes, we have follows function.

       o Symbolic Link
       o Real Name(long name)
       o File Attribute 
       o Time stamp
       o uid, gid
       o Devices
       o Relocated directories

   Except follows:

       o POSIX device number mapping

         There is some preliminary stuff in there that (ab-)uses the mknod
         system call, but this needs a writable filesystem
         
 3) should be called cdfs, as there are other ISO file system soon possible

   Not yet. Probably we should make another file system when the ECMA draft 
   is valid and do it. For doing Rock Ridge Support, I can use almost same
   code. So I just use the same file system interface...

 4) should have file handles implemented for use with NFS, etc

   Yes. we have already this one, and I based it for this release. 

 5) should have name translation enabled by mount flag

   Yes. we can disable the Rock Ridge Extension by follows option;

      "mount -t isofs -o -norrip /dev/cd0d /cdrom"

 6) should run as a user process, and not take up kernel space (cdroms
    are slow)

   Not yet.

 7) ECMA support.

   Not yet. we need not only a technical spec but also ECMA format
   cd-rom itself!

 8) Character set change by SVD ( multi SVD support )

   Not yet. We should also hack the other part of system as 8 bit
   clean. As far as I know, if you export the cdrom by NFS, the client
   can access the 8 bit clean (ie. Solaris Japanese with EUC code )

 9) Access checks in isofs_access

   Not yet.

 10) Support for generation numbers

   Yes. Default is to list only the last file (the one with the highest
   generation number). If you mount with -gen, all files are shown with
   their generation numbers. In both cases you can specify the generation
   number on opening files (if you happen to know it) or leave it off,
   when it will again find the last file.

 11) Support for extended attributes

   Yes. Since this requires an extra block buffer for the attributes
   this must be enabled on mounting with the option -extattr.

----------
Last update July 19, '93 by Atsushi Murai. (amurai@spec.co.jp)
Last update August 19, '93 by Wolfgang Solfrank. (ws@tools.de)
OpenPOWER on IntegriCloud