LL...

Start by making some discoveries of what a UNIX list type non-contiguous structured environment is. Then compare that, to a non-contiguous linklist type environment.

list....Start with an organizational index that contain individual address pointers to lists. Each list contains an ordered number of address pointers, that point to the physical combinations of bytes within a memory matrix making up a file. The combinational bytes can be anywhere on the memory matrix allowing for a non-contiguous environment. The pointers within the list know where to find and organize a file. This type of environment is very overhead burdened, for, as you create data, lists of pointers grow and grow and grow....etc. as well as the index.

Linklist...is not an ordered list of address pointers creating a file as above. This type of organizational method is what is called meta-data based. There's an index, as above, of address pointers such as FAT(file allocation table). Where one pointer within the index, points to the physical lead segment of a file. From that point, the balance of data segments are tied together with associated media-data within each segment....where segments carry an address pointer(meta-data) to the next corresponding segment of the file. There is an overhead to this, however, not to the extent of the above. The only thing that physically grows is the index, the actual file organization is carried within itself as media-data. With this, as above, the bytes of the file can be anywhere on the memory matrix allowing for a non-contiguous environment, the associated media-data pulls the file together form anywhere.

Contiguous....for this type system there is a start index, as the above, having individual address pointers, each pointing to the lead segment of a file. Unlike the two above, the file is pulled together by physical contact between data segments. The data segments have to be in exact line up in the memory matrix, physical contact ties them together in their ordered arrangement. There is no list of pointers organizing a file, nor is there media-data associated organizing the file...therefore they have to stay contiguously connected.

Keep in mind, that for each of the above, they are shadowed or paged to RAM under normal routine configurations in order to maintain integrity.

e.Digital utilizing flash hardware and patented discrete manipulation of a media-data based logical overlay of a memory matrix do not have to. This overlay can be organize contiguously or non-contiguously. With that, they can implement the attributes of any OS amid. IMO, for contiguous arrangement, it would still utilize the media-data of the system and pack data in contiguous fashion.

doni