freebsd-skq/sys/isofs/cd9660/TODO.hibler

$FreeBSD$

1. Investiate making ISOFS another UFS shared filesystem (ala FFS/MFS/LFS).
   Since it was modelled after the inode code, we might be able to merge
   them back.  It looks like a separate (but very similar) lookup routine
   will be needed due to the associated file stuff.

2. It would be nice to be able to use the vfs_cluster code.
   Unfortunately, if the logical block size is smaller than the page size,
   it won't work.  Also, if throughtput is relatively constant for any
   block size (as it is for the HP drive--150kbs) then clustering may not
   buy much (or may even hurt when vfs_cluster comes up with a large sync
   cluster).

3. Seems like there should be a "notrans" or some such mount option to show
   filenames as they really are without lower-casing.  Does this make sense?
Add $FreeBSD$ 2000-05-01 20:32:07 +00:00			$FreeBSD$

Import 4.4BSD-Lite2 onto the vendor branch, note that in the kernel, all files are off the vendor branch, so this should not change anything. A "U" marker generally means that the file was not changed in between the 4.4Lite and Lite-2 releases, and does not need a merge. "C" generally means that there was a change. [note, new file: cd9660_mount.h] 1996-03-11 19:20:10 +00:00			`1. Investiate making ISOFS another UFS shared filesystem (ala FFS/MFS/LFS).`
			`Since it was modelled after the inode code, we might be able to merge`
Fix typo: seperate -> separate. Seperate does not exist in the english language. 2001-02-06 11:21:58 +00:00			`them back. It looks like a separate (but very similar) lookup routine`
Import 4.4BSD-Lite2 onto the vendor branch, note that in the kernel, all files are off the vendor branch, so this should not change anything. A "U" marker generally means that the file was not changed in between the 4.4Lite and Lite-2 releases, and does not need a merge. "C" generally means that there was a change. [note, new file: cd9660_mount.h] 1996-03-11 19:20:10 +00:00			`will be needed due to the associated file stuff.`

			`2. It would be nice to be able to use the vfs_cluster code.`
			`Unfortunately, if the logical block size is smaller than the page size,`
			`it won't work. Also, if throughtput is relatively constant for any`
			`block size (as it is for the HP drive--150kbs) then clustering may not`
			`buy much (or may even hurt when vfs_cluster comes up with a large sync`
			`cluster).`

			`3. Seems like there should be a "notrans" or some such mount option to show`
			`filenames as they really are without lower-casing. Does this make sense?`