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]

1 files changed, 3 insertions, 11 deletions

diff --git a/sys/isofs/cd9660/TODO.hibler b/sys/isofs/cd9660/TODO.hibler
index 3501aa2..660b268 100644
--- a/sys/isofs/cd9660/TODO.hibler
+++ b/sys/isofs/cd9660/TODO.hibler
@@ -3,20 +3,12 @@
    them back.  It looks like a seperate (but very similar) lookup routine
    will be needed due to the associated file stuff.
 
-2. Make filesystem exportable.  This comes for free if stacked with UFS.
-   Otherwise, the ufs_export routines need to be elevated to vfs_* routines.
-	[ DONE - hibler ]
-
-3. If it can't be merged with UFS, at least get them in sync.  For example,
-   it could use the same style hashing routines as in ufs/ufs_ihash.c
-
-4. It would be nice to be able to use the vfs_cluster code.
+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).
 
-5. Seems like there should be a "notrans" or some such mount option to show
-   filenames as they really are without lower-casing, stripping of version
-   numbers, etc.  Does this make sense?
+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?