Dynamic Inode lists

[Brandon S. Allbery]

As quoted from <10301 at cit-vax.Caltech.Edu> by mangler at cit-vax.Caltech.Edu (Don Speck):
+---------------
| In article <28454 at apple.Apple.COM>, fair at Apple.COM (Erik E. Fair) writes:
| > In the referenced article, mangler at cit-vax.Caltech.Edu (Don Speck) writes:
| >	By the way, will someone please put the ilist into a file, so
| >	it can be dynamically extended?
| >
| > If you do that, how do you propose to allocate it, such that you don't
| > have to go seeking all over the disk to find the inode you're looking
| > for?
| 
| A file containing all the inodes would probably need only one indirect
| block on a BSD or V9 filesystem.  That indirect block is likely to remain
| in the buffer cache.
| (...)
| I'd mention where this idea has been used before, but some might find
| the example to be odious.
+---------------

"Damn the torpedoes; full speed ahead!"  It had a lot of good ideas, but
nobody took the time to implement them properly.  Pity, that.  The source is
TRSDOS (file DIR/SYS is the disk directory).

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery at ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery at hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser