[src/trunk]: src/sys/msdosfs simplify

[jdolecek <jdolecek%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/e263d4c09e68
branches:  trunk
changeset: 495801:e263d4c09e68
user:      jdolecek <jdolecek%NetBSD.org@localhost>
date:      Sun Aug 06 20:11:31 2000 +0000

description:
simplify

diffstat:

 sys/msdosfs/TODO |  18 +++++++-----------
 1 files changed, 7 insertions(+), 11 deletions(-)

diffs (23 lines):

diff -r 8d03757816ef -r e263d4c09e68 sys/msdosfs/TODO
--- a/sys/msdosfs/TODO  Sun Aug 06 19:49:53 2000 +0000
+++ b/sys/msdosfs/TODO  Sun Aug 06 20:11:31 2000 +0000
@@ -1,12 +1,8 @@
-# $NetBSD: TODO,v 1.5 2000/03/27 10:15:13 jdolecek Exp $
+# $NetBSD: TODO,v 1.6 2000/08/06 20:11:31 jdolecek Exp $
 
-- use the dirty flag Win95 OSR2 introduced, as noted in bin/5638
-- the fat cache (see msdosfs_fat.c, denode->de_fc[]) should prolly
-       hold _all_ clusters for directories - should speed up repetitive
-       scanning through whole directory when extracting an archive
-       into msdosfs filesystem (e.g. tar does unlink followed by create
-       and both these functions need to scan whole directory to check
-       if the file is or isn't there)
-       - doing something similar for files is probably not worth the
-         efford, because the files are scanned much less frequently
-         and might be big
+- use the dirty flag introduced by Win95 OSR2, as noted in bin/5638
+- the fat cache (see msdosfs_fat.c, denode->de_fc[]) should probably
+       hold all cluster numbers for directories to speed up file lookup;
+       doing the same for files is likely to not be worth the needed
+       memory, since they are often much bigger and scanned much less
+       frequently