Proverbs, aphorisms, quotations (English) | by Linux fortune |
=== ALL USERS PLEASE NOTE ======================== CAR and CDR now return extra values. The function CAR now returns two values. Since it has to go to the trouble to figure out if the object is carcdr-able anyway, we figured you might as well get both halves at once. For example, the following code shows how to destructure a cons (SOME-CONS) into its two slots (THE-CAR and THE-CDR): (MULTIPLE-VALUE-BIND (THE-CAR THE-CDR) (CAR SOME-CONS) ...) For symmetry with CAR, CDR returns a second value which is the CAR of the object. In a related change, the functions MAKE-ARRAY and CONS have been fixed so they don't allocate any storage except on the stack. This should hopefully help people who don't like using the garbage collector because it cold boots the machine so often. | |
=== ALL USERS PLEASE NOTE ======================== The garbage collector now works. In addition a new, experimental garbage collection algorithm has been installed. With SI:%DSK-GC-QLX-BITS set to 17, (NOT the default) the old garbage collection algorithm remains in force; when virtual storage is filled, the machine cold boots itself. With SI:%DSK-GC- QLX-BITS set to 23, the new garbage collector is enabled. Unlike most garbage collectors, the new gc starts its mark phase from the mind of the user, rather than from the obarray. This allows the garbage collection of significantly more Qs. As the garbage collector runs, it may ask you something like "Do you remember what SI:RDTBL-TRANS does?", and if you can't give a reasonable answer in thirty seconds, the symbol becomes a candidate for GCing. The variable SI:%GC-QLX-LUSER-TM governs how long the GC waits before timing out the user. | |
Imagine that Cray computer decides to make a personal computer. It has a 150 MHz processor, 200 megabytes of RAM, 1500 megabytes of disk storage, a screen resolution of 4096 x 4096 pixels, relies entirely on voice recognition for input, fits in your shirt pocket and costs $300. What's the first question that the computer community asks? "Is it PC compatible?" | |
Overall, the philosophy is to attack the availability problem from two complementary directions: to reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them. An interesting footnote to this design is that now a system failure can usually be considered to be the result of two program errors: the first, in the program that started the problem; the second, in the recovery routine that could not protect the system. -- A.L. Scherr, "Functional Structure of IBM Virtual Storage Operating Systems, Part II: OS/VS-2 Concepts and Philosophies," IBM Systems Journal, Vol. 12, No. 4. | |
Pause for storage relocation. | |
Proposed Additions to the PDP-11 Instruction Set: DC Divide and Conquer DMPK Destroy Memory Protect Key DO Divide and Overflow EMPC Emulate Pocket Calculator EPI Execute Programmer Immediately EROS Erase Read Only Storage EXCE Execute Customer Engineer HCF Halt and Catch Fire IBP Insert Bug and Proceed INSQSW Insert into queue somewhere (for FINO queues [First in never out]) PBC Print and Break Chain PDSK Punch Disk | |
There was once a programmer who worked upon microprocessors. "Look at how well off I am here," he said to a mainframe programmer who came to visit, "I have my own operating system and file storage device. I do not have to share my resources with anyone. The software is self-consistent and easy-to-use. Why do you not quit your present job and join me here?" The mainframe programmer then began to describe his system to his friend, saying: "The mainframe sits like an ancient sage meditating in the midst of the data center. Its disk drives lie end-to-end like a great ocean of machinery. The software is a multi-faceted as a diamond and as convoluted as a primeval jungle. The programs, each unique, move through the system like a swift-flowing river. That is why I am happy where I am." The microcomputer programmer, upon hearing this, fell silent. But the two programmers remained friends until the end of their days. -- Geoffrey James, "The Tao of Programming" | |
Two hundred years ago today, Irma Chine of White Plains, New York, was performing her normal housekeeping routines. She was interrupted by British soldiers who, rallying to the call of their supervisor, General Hughes, sought to gain control of the voter registration lists kept in her home. Masking her fear and thinking fast, Mrs. Chine quickly divided a nearby apple in two and deftly stored the list in its center. Upon entering, the British blatantly violated every conceivable convention, and, though they went through the house virtually bit by bit, their search was fruitless. They had to return empty handed. Word of the incident propagated rapidly through the region. This historic event became the first documented use of core storage for the saving of registers. | |
Overall, the philosophy is to attack the availability problem from two complementary directions: to reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them. An interesting footnote to this design is that now a system failure can usually be considered to be the result of two program errors: the first, in the program that started the problem; the second, in the recovery routine that could not protect the system. -- A. L. Scherr, "Functional Structure of IBM Virtual Storage Operating Systems, Part II: OS/VS-2 Concepts and Philosophies," IBM Systems Journal, Vol. 12, No. 4, 1973, pp. 382-400 | |
Canada Post doesn't really charge 32 cents for a stamp. It's 2 cents for postage and 30 cents for storage. -- Gerald Regan, Cabinet Minister, 12/31/83 Financial Post | |
I've built a better model than the one at Data General For data bases vegetable, animal, and mineral My OS handles CPUs with multiplexed duality; My PL/1 compiler shows impressive functionality. My storage system's better than magnetic core polarity, You never have to bother checking out a bit for parity; There isn't any reason to install non-static floor matting; My disk drive has capacity for variable formatting. I feel compelled to mention what I know to be a gloating point: There's lots of room in memory for variables floating-point, Which shows for input vegetable, animal, and mineral I've built a better model than the one at Data General. -- Steve Levine, "A Computer Song" (To the tune of "Modern Major General", from "Pirates of Penzance", by Gilbert & Sullivan) | |
Andries Brouwer wrote: > Linux is unreliable. > That is bad. Since your definition of reliability is a mathematical abstraction requiring infinite storage why don't you start by inventing infinitely large SDRAM chips, then get back to us ? - Alan Cox | |
A cow is a completely automated milk-manufacturing machine. It is encased in untanned leather and mounted on four vertical, movable supports, one at each corner. The front end of the machine, or input, contains the cutting and grinding mechanism, utilizing a unique feedback device. Here also are the headlights, air inlet and exhaust, a bumper and a foghorn. At the rear, the machine carries the milk-dispensing equipment as well as a built-in flyswatter and insect repeller. The central portion houses a hydro- chemical-conversion unit. Briefly, this consists of four fermentation and storage tanks connected in series by an intricate network of flexible plumbing. This assembly also contains the central heating plant complete with automatic temperature controls, pumping station and main ventilating system. The waste disposal apparatus is located to the rear of this central section. Cows are available fully-assembled in an assortment of sizes and colors. Production output ranges from 2 to 20 tons of milk per year. In brief, the main external visible features of the cow are: two lookers, two hookers, four stander-uppers, four hanger-downers, and a swishy-wishy. | |
Possessions increase to fill the space available for their storage. -- Ryan |