Diaper Punishment Clips

Auto-interview System Files "in V-TAPES? Technical Manuals

I said that Heritage / 1 does not use fixed disks (hard drives), at least occurring during childhood. The type of storage to which I mentally focused is the V-TAPE ", ie simulating a floppy disk comportamento a magnetic tape of the old days.

I've seen recently that I have not actually writing a file system for it not just format my floppy disks for use in low level "raw floppies," a concept used in real life today.

But the point that concerns me is another: How do you manage the OS to handle configuration files housed in the media so slow? Incidentally, I'm tempted to use an "open reel audio and storage as well.

The case is a typical Unix-like operating system is based on many files configuration, as well as shell-scripts to run. Would not it be then too costly-in terms of time-constant reading of files to tape or V-TAPE? On the other hand did few films and V-TAPES I will have to provide only for the exclusive use of the OS?

I think the answer is to keep these files loaded into memory all the time, or at least as long as there is memory available for applications. This usually leads me to a caching mechanism that involves not only the system files but everyone in general. CACHE

It's always interesting at the same time intricate. The system must retain the image of the files and decide priorities remove them when memory for other more urgent file being loaded (eg a program). And those priorities should be indicated somewhere ... such a configuration file!

Another way (parallel) to increase the efficiency of access to storage. For example, provide some means for my "open reel" can quickly find files on the tape that is mounted. It occurs to me, for example, that the machine count the rotations of the motor 'take' and on that basis provide "general direction" of the files stored on the tape. The machine speed rebobinaría of seaweed, but counting rounds, so that when considered to be close to the target, pursue Search for speed.

For this, the driver of the machine must have an internal memory (not memory map) to save a kind of directory, which was read from the tape itself at "mount-time."

The same problem (and perhaps more so) comes with my Run-Time Library (RTL), which should be available for different programs, but also occupies a significant place in memory.

interesting thing about all this is to explore how such work that our modern operating systems solved "easily" through the possession of an enormous disc, can be solved in an environment where estorage is low, slow and low capacity ... How they did in the 60s ... precisely that question.