Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!cwjcc!hal!ncoast!allbery From: allbery@ncoast.ORG (Brandon S. Allbery) Newsgroups: comp.unix.wizards Subject: Re: Dynamic Inode lists Message-ID: <13566@ncoast.ORG> Date: 15 Apr 89 16:03:19 GMT References: <10189@cit-vax.Caltech.Edu> <28454@apple.Apple.COM> <10301@cit-vax.Caltech.Edu> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: ca.unix Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 29 As quoted from <10301@cit-vax.Caltech.Edu> by mangler@cit-vax.Caltech.Edu (Don Speck): +--------------- | In article <28454@apple.Apple.COM>, fair@Apple.COM (Erik E. Fair) writes: | > In the referenced article, mangler@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@ncoast.org uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu Send comp.sources.misc submissions to comp-sources-misc@ NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser