``my method of choice would be to have ``ball 1`` connected to ``ball 2`` with a string, and then ``ball 2`` connected to ``ball 3`` with a string, etc. etc., and then store them all in one box in a big pile inside the box

then to retrieve all 10 balls in order takes only pulling one string.....much more efficient.``

correct....

This would be a representation of methods used by MSFT and would be considered an Index table(FAT or file allocation table)....requiring only one string attached to one nail in the board((there will be many pointers of a FAT organizing different Link lists(or string connections)).....giving a full recall for all the other balls in specific order.

Which system do you prefer now that you see the difference between Inode and Index ? One requires a mountain of overhead while the other does not...as far as the OS having to keep track.

Now when I speak of Inode and Index....there should be no problem of difference.... they`re both considered non-contiguous methods...as the balls can be all mixed up in the basket...yet you get specific recall from either method.

There is a third method....???

don`t get a head of your self with the other stuff.....different media require different addressing schemes....CHS(cylinder head sector) or LBA(logical block addressing...

doni