DEEn Dictionary De - En
DeEs De - Es
DePt De - Pt
 Vocabulary trainer

Spec. subjects Grammar Abbreviations Random search Preferences
Search in Sprachauswahl
Code
Search for:
Mini search box
 
Proverbs, aphorisms, quotations (English) by Linux fortune

Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of
code using nothing but vi or emacs. AAAAACK!
(Discussion in comp.os.linux.misc on the intuitiveness of commands, especially
Emacs.)
"I would rather spend 10 hours reading someone else's source code than
10 minutes listening to Musak waiting for technical support which isn't."
(By Dr. Greg Wettstein, Roger Maris Cancer Center)
We use Linux for all our mission-critical applications. Having the source code
means that we are not held hostage by anyone's support department.
(Russell Nelson, President of Crynwr Software)
descramble code needed from software company
Typo in the code
1: No code table for op: ++post
A bug in the code is worth two in the documentation.
        *** A NEW KIND OF PROGRAMMING ***

Do you want the instant respect that comes from being able to use technical
terms that nobody understands?  Do you want to strike fear and loathing into
the hearts of DP managers everywhere?  If so, then let the Famous Programmers'
School lead you on... into the world of professional computer programming.
They say a good programmer can write 20 lines of effective program per day.
With our unique training course, we'll show you how to write 20 lines of code
and lots more besides.  Our training course covers every programming language
in existence, and some that aren't.  You'll learn why the on/off switch for a
computer is so important, what the words *fatal error* mean, and who and what
you should blame when you make a mistake.

        Yes, I want the brochure describing this incredible offer.
        I enclose $1000 is small unmarked bills to cover the cost of
        postage and handling. (No live poultry, please.)

*** Our Slogan:  Top down programming for the masses. ***
        A novice asked the Master: "Here is a programmer that never designs,
documents, or tests his programs.  Yet all who know him consider him one of
the best programmers in the world.  Why is this?"
        The Master replies: "That programmer has mastered the Tao.  He has
gone beyond the need for design; he does not become angry when the system
crashes, but accepts the universe without concern.  He has gone beyond the
need for documentation; he no longer cares if anyone else sees his code.  He
has gone beyond the need for testing; each of his programs are perfect within
themselves, serene and elegant, their purpose self-evident.  Truly, he has
entered the mystery of the Tao."
                -- Geoffrey James, "The Tao of Programming"
        A novice programmer was once assigned to code a simple financial
package.
        The novice worked furiously for many days, but when his master
reviewed his program, he discovered that it contained a screen editor, a set
of generalized graphics routines, and artificial intelligence interface,
but not the slightest mention of anything financial.
        When the master asked about this, the novice became indignant.
"Don't be so impatient," he said, "I'll put the financial stuff in eventually."
                -- Geoffrey James, "The Tao of Programming"
===  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  ========================

Compiler optimizations have been made to macro expand LET into a WITHOUT-
INTERRUPTS special form so that it can PUSH things into a stack in the
LET-OPTIMIZATION area, SETQ the variables and then POP them back when it's
done.  Don't worry about this unless you use multiprocessing.
Note that LET *could* have been defined by:

        (LET ((LET '`(LET ((LET ',LET))
                        ,LET)))
        `(LET ((LET ',LET))
                ,LET))

This is believed to speed up execution by as much as a factor of 1.01 or
3.50 depending on whether you believe our friendly marketing representatives.
This code was written by a new programmer here (we snatched him away from
Itty Bitti Machines where he was writing COUGHBOL code) so to give him
confidence we trusted his vows of "it works pretty well" and installed it.
As of next week, passwords will be entered in Morse code.
As part of an ongoing effort to keep you, the Fortune reader, abreast of
the valuable information the daily crosses the USENET, Fortune presents:

News articles that answer *your* questions, #1:

        Newsgroups: comp.sources.d
        Subject: how do I run C code received from sources
        Keywords: C sources
        Distribution: na

        I do not know how to run the C programs that are posted in the
        sources newsgroup.  I save the files, edit them to remove the
        headers, and change the mode so that they are executable, but I
        cannot get them to run.  (I have never written a C program before.)

        Must they be compiled?  With what compiler?  How do I do this?  If
        I compile them, is an object code file generated or must I generate
        it explicitly with the > character?  Is there something else that
        must be done?
Beware of bugs in the above code; I have only proved it correct, not tried it.
                -- Donald Knuth
Beware the new TTY code!
C Code.
C Code Run.
Run, Code, RUN!
        PLEASE!!!!
#define BITCOUNT(x)        (((BX_(x)+(BX_(x)>>4)) & 0x0F0F0F0F) % 255)
#define  BX_(x)                ((x) - (((x)>>1)&0x77777777)                        \
                             - (((x)>>2)&0x33333333)                        \
                             - (((x)>>3)&0x11111111))

                -- really weird C code to count the number of bits in a word
Deliver yesterday, code today, think tomorrow.
Does a good farmer neglect a crop he has planted?
Does a good teacher overlook even the most humble student?
Does a good father allow a single child to starve?
Does a good programmer refuse to maintain his code?
                -- Geoffrey James, "The Tao of Programming"
Don't get suckered in by the comments -- they can be terribly misleading.
Debug only code.
                -- Dave Storer
Fellow programmer, greetings!  You are reading a letter which will bring
you luck and good fortune.  Just mail (or UUCP) ten copies of this letter
to ten of your friends.  Before you make the copies, send a chip or
other bit of hardware, and 100 lines of 'C' code to the first person on the
list given at the bottom of this letter.  Then delete their name and add
yours to the bottom of the list.

Don't break the chain!  Make the copy within 48 hours.  Gerald R. of San
Diego failed to send out his ten copies and woke the next morning to find
his job description changed to "COBOL programmer."  Fred A. of New York sent
out his ten copies and within a month had enough hardware and software to
build a Cray dedicated to playing Zork.  Martha H. of Chicago laughed at
this letter and broke the chain.  Shortly thereafter, a fire broke out in
her terminal and she now spends her days writing documentation for IBM PC's.

Don't break the chain!  Send out your ten copies today!
For example, if \thinmskip = 3mu, this makes \thickmskip = 6mu.  But if
you also want to use \skip12 for horizontal glue, whether in math mode or
not, the amount of skipping will be in points (e.g., 6pt).  The rule is
that glue in math mode varies with the size only when it is an \mskip;
when moving between an mskip and ordinary skip, the conversion factor
1mu=1pt is always used.  The meaning of '\mskip\skip12' and
'\baselineskip=\the\thickmskip' should be clear.
                -- Donald Knuth, TeX 82 -- Comparison with TeX80
I've noticed several design suggestions in your code.
If the code and the comments disagree, then both are probably wrong.
                -- Norm Schryer
        In the beginning there was data.  The data was without form and
null, and darkness was upon the face of the console; and the Spirit of
IBM was moving over the face of the market.  And DEC said, "Let there
be registers"; and there were registers.  And DEC saw that they
carried; and DEC separated the data from the instructions.  DEC called
the data Stack, and the instructions they called Code.  And there was
evening and there was morning, one interrupt.
                -- Rico Tudor, "The Story of Creation or, The Myth of Urk"
Introducing, the 1010, a one-bit processor.

INSTRUCTION SET
        Code        Mnemonic        What
        0        NOP                No Operation
        1        JMP                Jump (address specified by next 2 bits)

Now Available for only 12 1/2 cents!
        It is a period of system war.  User programs, striking from a hidden
directory, have won their first victory against the evil Administrative Empire.
During the battle, User spies managed to steal secret source code to the
Empire's ultimate program: the Are-Em Star, a privileged root program with
enough power to destroy an entire file structure.  Pursued by the Empire's
sinister audit trail, Princess _LPA0 races ~ aboard her shell script,
custodian of the stolen listings that could save her people, and restore
freedom and games to the network...
                -- DECWARS
It turned out that the worm exploited three or four different holes in the
system.  From this, and the fact that we were able to capture and examine
some of the source code, we realized that we were dealing with someone very
sharp, probably not someone here on campus.
                -- Dr. Richard LeBlanc, associate professor of ICS, in
                   Georgia Tech's campus newspaper after the Internet worm.
Life would be so much easier if we could just look at the source code.
        -- Dave Olson
Make sure your code does nothing gracefully.
        n = ((n >>  1) & 0x55555555) | ((n <<  1) & 0xaaaaaaaa);
        n = ((n >>  2) & 0x33333333) | ((n <<  2) & 0xcccccccc);
        n = ((n >>  4) & 0x0f0f0f0f) | ((n <<  4) & 0xf0f0f0f0);
        n = ((n >>  8) & 0x00ff00ff) | ((n <<  8) & 0xff00ff00);
        n = ((n >> 16) & 0x0000ffff) | ((n << 16) & 0xffff0000);

                -- C code which reverses the bits in a word.
        Now she speaks rapidly.  "Do you know *why* you want to program?"
        He shakes his head.  He hasn't the faintest idea.
        "For the sheer *joy* of programming!" she cries triumphantly.  
"The joy of the parent, the artist, the craftsman.  "You take a program,
born weak and impotent as a dimly-realized solution.  You nurture the
program and guide it down the right path, building, watching it grow ever
stronger.  Sometimes you paint with tiny strokes, a keystroke added here,
a keystroke changed there."  She sweeps her arm in a wide arc.  "And other
times you savage whole *blocks* of code, ripping out the program's very
*essence*, then beginning anew.  But always building, creating, filling the
program with your own personal stamp, your own quirks and nuances.  Watching
the program grow stronger, patching it when it crashes, until finally it can
stand alone -- proud, powerful, and perfect.  This is the programmer's finest
hour!"  Softly at first, then louder, he hears the strains of a Sousa march.
"This ... this is your canvas! your clay!  Go forth and create a masterwork!"
Okay, Okay -- I admit it.  You didn't change that program that worked
just a little while ago; I inserted some random characters into the
executable.  Please forgive me.  You can recover the file by typing in
the code over again, since I also removed the source.
        Price Wang's programmer was coding software.  His fingers danced upon
the keyboard.  The program compiled without an error message, and the program
ran like a gentle wind.
        Excellent!" the Price exclaimed, "Your technique is faultless!"
        "Technique?" said the programmer, turning from his terminal, "What I
follow is the Tao -- beyond all technique.  When I first began to program I
would see before me the whole program in one mass.  After three years I no
longer saw this mass.  Instead, I used subroutines.  But now I see nothing.
My whole being exists in a formless void.  My senses are idle.  My spirit,
free to work without a plan, follows its own instinct.  In short, my program
writes itself.  True, sometimes there are difficult problems.  I see them
coming, I slow down, I watch silently.  Then I change a single line of code
and the difficulties vanish like puffs of idle smoke.  I then compile the
program.  I sit still and let the joy of the work fill my being.  I close my
eyes for a moment and then log off."
        Price Wang said, "Would that all of my programmers were as wise!"
                -- Geoffrey James, "The Tao of Programming"
Real computer scientists don't comment their code.  The identifiers are
so long they can't afford the disk space.
Real computer scientists don't write code.  They occasionally tinker with
`programming systems', but those are so high level that they hardly count
(and rarely count accurately; precision is for applications).
Real programmers don't comment their code.  It was hard to write, it
should be hard to understand.
The fountain code has been tightened slightly so you can no longer dip
objects into a fountain or drink from one while you are floating in mid-air
due to levitation.
        Teleporting to hell via a teleportation trap will no longer occur
if the character does not have fire resistance.
                -- README file from the NetHack game
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #10: SIMPLE

SIMPLE is an acronym for Sheer Idiot's Monopurpose Programming Language
Environment.  This language, developed at the Hanover College for
Technological Misfits, was designed to make it impossible to write code
with errors in it.  The statements are, therefore, confined to BEGIN,
END and STOP.  No matter how you arrange the statements, you can't make
a syntax error.  Programs written in SIMPLE do nothing useful.  Thus
they achieve the results of programs written in other languages without
the tedious, frustrating process of testing and debugging.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #16: C-

This language was named for the grade received by its creator when he
submitted it as a class project in a graduate programming class.  C- is best
described as a "low-level" programming language.  In fact, the language
generally requires more C- statements than machine-code statements to
execute a given task.  In this respect, it is very similar to COBOL.
The number of computer scientists in a room is inversely proportional
to the number of bugs in their code.
                      THE STORY OF CREATION
                               or
                         THE MYTH OF URK

In the beginning there was data.  The data was without form and null, and
darkness was upon the face of the console; and the Spirit of IBM was moving
over the face of the market.  And DEC said, "Let there be registers;" and
there were registers.  And DEC saw that they carried; and DEC separated the
data from the instructions.  DEC called the data Stack, and the instructions
they called Code.  And there was evening and there was morning, one interrupt
...
                -- Rico Tudor
Thus spake the master programmer:
        "When you have learned to snatch the error code from
        the trap frame, it will be time for you to leave."
                -- Geoffrey James, "The Tao of Programming"
"We invented a new protocol and called it Kermit, after Kermit the Frog,
star of "The Muppet Show." [3]

[3]  Why?  Mostly because there was a Muppets calendar on the wall when we
were trying to think of a name, and Kermit is a pleasant, unassuming sort of
character.  But since we weren't sure whether it was OK to name our protocol
after this popular television and movie star, we pretended that KERMIT was an
acronym; unfortunately, we could never find a good set of words to go with the
letters, as readers of some of our early source code can attest.  Later, while
looking through a name book for his forthcoming baby, Bill Catchings noticed
that "Kermit" was a Celtic word for "free", which is what all Kermit programs
should be, and words to this effect replaced the strained acronyms in our
source code (Bill's baby turned out to be a girl, so he had to name her Becky
instead).  When BYTE Magazine was preparing our 1984 Kermit article for
publication, they suggested we contact Henson Associates Inc. for permission
to say that we did indeed name the protocol after Kermit the Frog.  Permission
was kindly granted, and now the real story can be told.  I resisted the
temptation, however, to call the present work "Kermit the Book."
                -- Frank da Cruz, "Kermit - A File Transfer Protocol"
Your code should be more efficient!
"In the face of entropy and nothingness, you kind of have to pretend it's not
there if you want to keep writing good code."  -- Karl Lehenbauer
The fountain code has been tightened slightly so you can no longer dip objects
into a fountain or drink from one while you are floating in mid-air due to
levitation.

Teleporting to hell via a teleportation trap will no longer occur if the
character does not have fire resistance.

- README file from the NetHack game
...Veloz is indistinguishable from hundreds of other electronics businesses
in the Valley, run by eager young engineers poring over memory dumps late
into the night.  The difference is that a bunch of self-confessed "car nuts"
are making money doing what they love: writing code and driving fast.
-- "Electronics puts its foot on the gas", IEEE Spectrum, May 88
  "Emergency!"  Sgiggs screamed, ejecting himself from the tub like it was
a burning car.  "Dial 'one'!  Get room service!  Code red!"  Stiggs was on
the phone immediately, ordering more rose blossoms, because, according to
him, the ones floating in the tub had suddenly lost their smell.  "I demand
smell," he shrilled.  "I expecting total uninterrupted smell from these
f*cking roses."

  Unfortunately, the service captain didn't realize that the Stiggs situation
involved fifty roses.  "What am I going to do with this?" Stiggs sneered at
the weaseling hotel goon when he appeared at our door holding a single flower
floating in a brandy glass.  Stiggs's tirade was great.  "Do you see this
bathtub?  Do you notice any difference between the size of the tub and the
size of that spindly wad of petals in your hand?  I need total bath coverage.
I need a completely solid layer of roses all around me like puffing factories
of smell, attacking me with their smell and power-ramming big stinking
concentrations of rose odor up my nostrils until I'm wasted with pleasure."
It wasn't long before we got so dissatisfied with this incompetence that we
bolted.
-- The Utterly Monstrous, Mind-Roasting Summer of O.C. and Stiggs,
   National Lampoon, October 1982
FORTRAN?  The syntactically incorrect statement "DO 10 I = 1.10" will parse and
generate code creating a variable, DO10I, as follows: "DO10I = 1.10"  If that
doesn't terrify you, it should.
If you permit yourself to read meanings into (rather than drawing meanings out
of) the evidence, you can draw any conclusion you like.
-- Michael Keith, "The Bar-Code Beast", The Skeptical Enquirer Vol 12 No 4 p 416
"Pseudocode can be used to some extent to aid the maintenance
process.  However, pseudocode that is highly detailed -
approaching the level of detail of the code itself - is not of
much use as maintenance documentation.  Such detailed
documentation has to be maintained almost as much as the code,
thus doubling the maintenance burden.  Furthermore, since such
voluminous pseudocode is too distracting to be kept in the
listing itself, it must be kept in a separate folder.  The
result: Since pseudocode - unlike real code - doesn't have to be
maintained, no one will maintain it.  It will soon become out of
date and everyone will ignore it.  (Once, I did an informal
survey of 42 shops that used pseudocode.  Of those 42, 0 [zero!],
found that it had any value as maintenance documentation."
         --Meilir Page-Jones, "The Practical Guide to Structured
           Design", Yourdon Press (c) 1988
    UNIX Shell is the Best Fourth Generation Programming Language

    It is the UNIX shell that makes it possible to do applications in a small
    fraction of the code and time it takes in third generation languages.  In
    the shell you process whole files at a time, instead of only a line at a
    time.  And, a line of code in the UNIX shell is one or more programs,
    which do more than pages of instructions in a 3GL.  Applications can be
    developed in hours and days, rather than months and years with traditional
    systems.  Most of the other 4GLs available today look more like COBOL or
    RPG, the most tedious of the third generation lanaguages.

"UNIX Relational Database Management:  Application Development in the UNIX
Environment" by Rod Manis, Evan Schaffer, and Robert Jorgensen.  Prentice
Hall Software Series.  Brian Kerrighan, Advisor.  1988.
"Little else matters than to write good code."
-- Karl Lehenbauer
To write good code is a worthy challenge, and a source of civilized delight.
-- stolen and paraphrased from William Safire
"An ounce of prevention is worth a ton of code."
-- an anonymous programmer
"If the code and the comments disagree, then both are probably wrong."
-- Norm Schryer
#define BITCOUNT(x)        (((BX_(x)+(BX_(x)>>4)) & 0x0F0F0F0F) % 255)
#define  BX_(x)                ((x) - (((x)>>1)&0x77777777)                        \
                             - (((x)>>2)&0x33333333)                        \
                             - (((x)>>3)&0x11111111))

-- really weird C code to count the number of bits in a word
World War Three can be averted by adherence to a strictly enforced dress code!
ASCII:
        The control code for all beginning programmers and those who would
        become computer literate.  Etymologically, the term has come down as
        a contraction of the often-repeated phrase "ascii and you shall
        receive."
                -- Robb Russon
Eagleson's Law:
        Any code of your own that you haven't looked at for six or more
        months, might as well have been written by someone else.  (Eagleson
        is an optimist, the real number is more like three weeks.)
flowchart, n. & v.:
        [From flow "to ripple down in rich profusion, as hair" + chart
"a cryptic hidden-treasure map designed to mislead the uninitiated."]
1. n. The solution, if any, to a class of Mascheroni construction
problems in which given algorithms require geometrical representation
using only the 35 basic ideograms of the ANSI template.  2. n. Neronic
doodling while the system burns.  3. n. A low-cost substitute for
wallpaper.  4. n.  The innumerate misleading the illiterate.  "A
thousand pictures is worth ten lines of code." -- The Programmer's
Little Red Vade Mecum, Mao Tse T'umps.  5. v.intrans. To produce
flowcharts with no particular object in mind.  6. v.trans. To obfuscate
(a problem) with esoteric cartoons.
                -- Stan Kelly-Bootle, "The Devil's DP Dictionary"
standards, n.:
        The principles we use to reject other people's code.
                        It's grad exam time...
COMPUTER SCIENCE
        Inside your desk you'll find a listing of the DEC/VMS operating
system in IBM 1710 machine code. Show what changes are necessary to convert
this code into a UNIX Berkeley 7 operating system.  Prove that these fixes are
bug free and run correctly. You should gain at least 150% efficiency in the
new system.  (You should take no more than 10 minutes on this question.)

MATHEMATICS
        If X equals PI times R^2, construct a formula showing how long
it would take a fire ant to drill a hole through a dill pickle, if the
length-girth ratio of the ant to the pickle were 98.17:1.

GENERAL KNOWLEDGE
Describe the Universe.  Give three examples.
The Commandments of the EE:

(9)        Trifle thee not with radioactive tubes and substances lest thou
        commence to glow in the dark like a lightning bug, and thy wife be
        frustrated and have not further use for thee except for thy wages.
(10)        Commit thou to memory all the words of the prophets which are
        written down in thy Bible which is the National Electrical Code,
        and giveth out with the straight dope and consoleth thee when
        thou hast suffered a ream job by the chief electrician.
(11)        When thou muckest about with a device in an unthinking and/or
        unknowing manner, thou shalt keep one hand in thy pocket.  Better
        that thou shouldest keep both hands in thy pockets than
        experimentally determine the electrical potential of an
        innocent-seeming device.
And now your toner's toney,                Disk blocks aplenty
And your paper near pure white,                Await your laser drawn lines,
The smudges on your soul are gone        Your intricate fonts,
And your output's clean as light..        Your pictures and signs.

We've labored with your father,                Your amputative absence
The venerable XGP,                        Has made the Ten dumb,
But his slow artistic hand,                Without you, Dover,
Lacks your clean velocity.                We're system untounged-

Theses and papers                         DRAW Plots and TEXage
And code in a queue                        Have been biding their time,
Dover, oh Dover,                        With LISP code and programs,
We've been waiting for you.                And this crufty rhyme.

Dover, oh Dover,                Dover, oh Dover, arisen from dead.
We welcome you back,                Dover, oh Dover, awoken from bed.
Though still you may jam,        Dover, oh Dover, welcome back to the Lab.
You're on the right track.        Dover, oh Dover, we've missed your clean
                                        hand...
Eleanor Rigby
        Sits at the keyboard
        And waits for a line on the screen
Lives in a dream
Waits for a signal
        Finding some code
        That will make the machine do some more.
What is it for?

All the lonely users, where do they all come from?
All the lonely users, why does it take so long?

Hacker MacKensie
Writing the code for a program that no one will run
It's nearly done
Look at him working, fixing the bugs in the night when there's
        nobody there.
What does he care?

All the lonely users, where do they all come from?
All the lonely users, why does it take so long?
Ah, look at all the lonely users.
Ah, look at all the lonely users.
How doth the VAX's C-compiler
        Improve its object code.
And even as we speak does it
        Increase the system load.

How patiently it seems to run
        And spit out error flags,
While users, with frustration, all
        Tear their clothes to rags.
If a system is administered wisely,
its users will be content.
They enjoy hacking their code
and don't waste time implementing
labor-saving shell scripts.
Since they dearly love their accounts,
they aren't interested in other machines.
There may be telnet, rlogin, and ftp,
but these don't access any hosts.
There may be an arsenal of cracks and malware,
but nobody ever uses them.
People enjoy reading their mail,
take pleasure in being with their newsgroups,
spend weekends working at their terminals,
delight in the doings at the site.
And even though the next system is so close
that users can hear its key clicks and biff beeps,
they are content to die of old age
without ever having gone to see it.
In the early morning queue,
With a listing in my hand.
With a worry in my heart,        There on terminal number 9,
Waitin' here in CERAS-land.        Pascal run all set to go.
I'm a long way from sleep,        But I'm waitin' in the queue,
How I miss a good meal so.        With this code that ever grows.
In the early mornin' queue,        Now the lobby chairs are soft,
With no place to go.                But that can't make the queue move fast.
                                Hey, there it goes my friend,
                                I've moved up one at last.
                -- Ernest Adams, "Early Morning Queue", to "Early
                   Morning Rain" by G. Lightfoot
She can kill all your files;
She can freeze with a frown.
And a wave of her hand brings the whole system down.
And she works on her code until ten after three.
She lives like a bat but she's always a hacker to me.
                -- Apologies to Billy Joel
They told me you had proven it                When they discovered our results
        About a month before.                        Their hair began to curl
The proof was valid, more or less        Instead of understanding it
        But rather less than more.                We'd run the thing through PRL.

He sent them word that we would try        Don't tell a soul about all this
        To pass where they had failed                For it must ever be
And after we were done, to them                A secret, kept from all the rest
        The new proof would be mailed.                Between yourself and me.

My notion was to start again
        Ignoring all they'd done
We quickly turned it into code
        To see if it would run.
To code the impossible code,                This is my quest --
To bring up a virgin machine,                To debug that code,
To pop out of endless recursion,        No matter how hopeless,
To grok what appears on the screen,        No matter the load,
                                        To write those routines
To right the unrightable bug,                Without question or pause,
To endlessly twiddle and thrash,        To be willing to hack FORTRAN IV
To mount the unmountable magtape,        For a heavenly cause.
To stop the unstoppable crash!                And I know if I'll only be true
                                        To this glorious quest,
And the queue will be better for this,        That my code will run CUSPy and calm,
That one man, scorned and                When it's put to the test.
        destined to lose,
Still strove with his last allocation
To scrap the unscrappable kludge!
                -- To "The Impossible Dream", from Man of La Mancha
Do not read this fortune under penalty of law.
Violators will be prosecuted.
(Penal Code sec. 2.3.2 (II.a.))
"Ford had his own code of ethics. It wasn't much of one,
but it was his and he stuck by it, more or less. One rule
he made was never to buy his own drinks. He wasn't sure if
that counted as an ethic, but you have to go with what
you've got. "
"The IETF motto is 'rouch consesus and running code'"
  
  -- Scott Bradner (Open Sources, 1999 O'Reilly and Associates)
I once heard Bill Gates say, "WHAT?!?!  Netscape caused an invalid page
fault!?!  Only Microsoft programs have the code to do that!"
You Might be a Microsoft Employee If...

1. When a Microsoft program crashes for the millionth time, you say "Oh,
    well!" and reboot without any negative thoughts
2. The Windows 95 startup screen (the clouds) makes you feel all warm and
    fuzzy inside
3. You fully understand why Windows 95's Shutdown Option has to be
    accessed from the Start Menu
4. You believe Internet Explorer's security flaws were slipped in by a
    crack team of Netscape programmers
5. You keep valuable papers near your fireplace. Therefore, you are
    comfortable with Windows 95's "may-delete-it-at-anytime" philosophy
6. You're the Bob that Microsoft Bob was named after
7. Instead of "I'd rather be fishing," your bumper sticker says, "I'd
    rather be writing buggy Microsoft code"
8. You know the technical difference between OLE 1.0 and OLE 2.0
9. You've ever completed your income taxes while waiting for Windows 95
    to boot, and didn't think anything of it
10. You run Solitaire more than any other program, and therefore you
    consider your computer a Dedicated Solitaire Engine (DSE)
Windows NT source code now available... download WIN2000.BAS now!

   -- From a Slashdot.org post
It's ten o'clock. Do you know where your source code is?

   -- From a Slashdot.org post
It's ten o'clock. Do you know where your source code is?
'Kitchen Sink' OS Announced

Coding has begun on a new operating system code named 'Kitchen Sink'. The new
OS will be based entirely on GNU Emacs. One programmer explained, "Since many
hackers spend a vast amount of their time in Emacs, why not just make it the
operating system?" When asked about the name, he responded, "Well, it has been
often said that Emacs has everything except a kitchen sink. Now it will."

One vi advocate said, "What the hell?!?! Those Emacs people are nuts. It seems
that even with a programming language, a web browser, and God only knows what
else built into their text editor, they're still not satisfied. Now they want
it to be an operating system. Hell, even Windows ain't that bloated!"
Stallman's Latest Proclamation

Richard M. Stallman doesn't want you to say "Windows" anymore. He is now
advocating that people call this OS by its real name:
Microsoft-Xerox-Apple-Windows. This proclamation comes on the heels of his
controversial stand that Linux should be called GNU/Linux. RMS explained in a
Usenet posting, "Calling Microsoft's OS 'Windows' is a grave inaccuracy. Xerox
and Apple both contributed significant ideas and innovations to this OS. Why
should Microsoft get all the credit?"

RMS also hinted that people shouldn't refer to Microsoft's web browser as IE.
"It should really be called Microsoft-Spyglass-Mosaic-Internet-Explorer. Again,
how much credit does Microsoft really deserve for this product? Much of the
base code was licensed from Spyglass."

Many industry pundits are less than thrilled about RMS' proclamation. The
editor of Windows Magazine exclaimed, "What?!?! Yeah, we'll rename our magazine
Microsoft-Xerox-Apple-Windows Magazine. That just rolls off the tongue!" A
Ziff-Davis columnist noted, "Think of all the wasted space this would cause. If
we spelled out everything like this, we'd have headlines like, 'Microsoft
Releases Service Pack 5 for Microsoft-Xerox-Apple-Windows Neutered Technology
4.0' Clearly this is unacceptable."
Microsoft Open Source Solitaire

REDMOND, WA -- In a first attempt at "embrace-and-extend" of open source
software, Microsoft will release its popular Solitaire and FreeCell games as
open source under the MILA (Microsoft Innovative License Agreement).
According to a Microsoft press release, the Visual C++ source code for the
two games will be available from the Microsoft website "in the first quarter"
(no year was specified).

Industry pundits hail the move as revolutionary.  "Microsoft's release of its
most popular Windows feature as open source software demonstrates just how
innovative the company really is.  The DoJ is clearly barking up the wrong
tree," wrote one Ziff-Davis flunkie. One executive at a large company said,
"Freely available source code is the best idea Microsoft has ever invented."

One Linux developer told Humorix, "Let's just hope some fool doesn't try to
port this thing to Linux.  Imagine the havoc that could ensue if a bunch of
core Linux contributors downloaded Solitaire and became addicted to it.  It
would be a disaster!  Linux and open source development would grind to a halt
while the hackers wasted their time playing Solitaire or FreeCell.  'Just one
more game...' they would say."
Microsoft ActivePromo Campaign: "Frequent Upgrade Points"

Microsoft's PR masterminds are planning a massive marketing campaign,
code-named "ActivePromo 2000", to promote the upcoming release of Windows
2000 (scheduled for February 2001).  This marketing campaign will include a
"Frequent Upgrade Points" promotion.

Customers who purchase upgrades to Windows, Office, or other Microsoft
"solutions" will receive "frequent upgrade points" (FUPs) when they register
online.  These points, like Frequent Flyer Miles, can be redeemed in the
future for discounts on other Microsoft upgrades. This program, combined
with the fact that older versions of some Microsoft programs have glaring
Y2K problems, should be enough to convince many people to shell out big
bucks to upgrade to a more bloated Microsoft operating system. The company
hopes to eradicate 99% of Windows 3.x installations by 2003.
Microsoft ActivePromo Campaign: "Match Vaporware & Win!"

Microsoft's PR masterminds are planning a massive marketing campaign,
code-named "ActivePromo 2000", to promote the upcoming release of Windows
2000 (scheduled for February 2001).  This marketing campaign will include a
"Match Vaporware & Win!" promotion.

Microsoft will team up with a major fast-food chain (McDonalds, probably,
since it has the largest market share, but Burger King is another
possibility) for a special Windows 2000 promotion.  With every combo meal
purchase, the customer will receive a game token containing a date on it. If
the official release of Windows 2000 is on that date, the customer can
redeem the token for a variety of prizes -- ranging from a "lifetime supply"
of Windows upgrades, to 25,000 shares of Microsoft stock.
Microsoft ActivePromo Campaign: "What Slogan Do You Want to See Tommorrow?"

Microsoft's PR masterminds are planning a massive marketing campaign,
code-named "ActivePromo 2000", to promote the upcoming release of Windows
2000 (scheduled for February 2001).  This marketing campaign will include a
"What Slogan Do You Want to See Tommorrow?" promotion.

Children under age 16 will have to opportunity to create their own Microsoft
slogan to replace the aging "Where Do You Want to Go Today?"(R) motto.
Microsoft will set up a special email alias where children can submit their
entries along with detailed personal and demographic information (for
verification purposes, of course).  A panel of Microsoft employees will
select a winning entry, which will become the official slogan.  The winner
and his/her family will receive an all-expense paid week-long vacation to
Redmond, WA ("The Vacation Capital of East Central Washington State"),
including a guided tour of the Microsoft campus and a personal ten minute
photo-opportunity with Chairman Bill.

We personally believe that "Don't Think About Going Anywhere Else Today"
would make a perfect Microsoft slogan.  "Crashes Are Normal" might also be a
good choice.
Microsoft ActivePromo Campaign: "Windows Competitive Upgrade Offer"

Microsoft's PR masterminds are planning a massive marketing campaign,
code-named "ActivePromo 2000", to promote the upcoming release of Windows
2000 (scheduled for February 2001).  This marketing campaign will include a
"Windows Competitive Upgrade Offer" promotion.

Users of non-Microsoft operating systems (Linux in particular) will be given
the opportunity to trade-in their present OS for a free copy of Windows 98
(or NT 4.0) and Office 97.  People (all three of them) who want to
participate in this program will have to:

1. Mail their operating system's floppy disks or CD-ROMs to Microsoft

2. Agree to a two year contract with the Microsoft Network.

3. Agree (in writing) to the Competitive Upgrade License Agreement; one of
the terms of which is that the user may not install, copy, or otherwise use
a non-Microsoft OS for five years.
Is Windows Antique?

SILICON VALLEY -- The first ever antique mall devoted to computers has
opened its doors deep in the heart of Silicon Valley.  Named "Stacks
of Antiqueues", the new mall features obsolete hardware, old software,
and other curiosities that only a nerd would want to buy.  The mall
also features a whole collection of Microsoft software, which, as can
be expected, has the Redmond giant up in arms.

The mall, founded by a group of Linux, FreeBSD, and BeOS users, has a whole
section devoted to Microsoft "antiques".  Offerings range from a rare
(and expensive) copy of Windows 1.0 all the way up to Windows 98.  All
versions of DOS from 1.0 up are available, in addition to such Microsoft
products as Bob, Profit, and Multiplan.

Bob Hinesdorf, one of the mall's founders, defends the decision to
include Microsoft products in its selection of antique computer stuff.
"Windows 98 is surely antique; it's based on 16 bit Windows 3.x code,
which was based on 16 bit DOS code, which was based loosely on 8 bit
CP/M."
Open Source Irrational Constant

BREEZEWOOD, PA -- In a revelation that could rock the foundations of
science, a researcher in Pennsylvania has discovered that the digits of the
irrational constant PI encode a version of the Linux kernel.  "I can't
believe it," the researcher, Neil Hoffman, exclaimed.  "And yet, here I am
staring at what appears to be the source code for Linux kernel 5.0.0.
Needless to say, my whole world-view has changed..."

Hoffman explained, "My algorithm, which applies several dozen conversions and
manipulations to each digit of PI, spits out plain vanilla ASCII characters
that happen to form the source code for the Linux kernel."

Many members of the scientific community are skeptical.  One One
mathematician who has memorized the digits of PI to 10,000 places said,
"This is the kind of nonsense one would expect to find in a tabloid such as
the National Mathematics Enquirer.  Or a Linux fortune(6) file.  Hoffman's
'discovery' is obviously a hoax designed to secure government research
grants."

In a related matter, we have received an unconfirmed report that a region of
the Mandelbrot fractal contains what appear to be the words "LINUS TORVALDS
WAS HERE".  In addition, the words "TRANSMETA: THIS SECRET MESSAGE IS NOT
HERE YET" supposedly appear within the depths of the Julia Set.
Attack of the Tuxissa Virus

What started out as a prank posting to comp.os.linux.advocacy yesterday has
turned into one of the most significant viruses in computing history.
The creator of the virus, who goes by the moniker "Anonymous Longhair",
modified the Melissa virus to install Linux on infected machines.

"It's a work of art," one Linux advocate told Humorix after he looked
through the Tuxissa virus source code.  "This virus goes well beyond the
feeble troublemaking of Melissa.  It actually configures a UMSDOS partition
on the user's hard drive and then downloads and installs a stripped-down
version of Slackware Linux."

The email message that the virus is attached to has the subject "Important
Message About Windows Security".  The text of the body says, "I want to let
you know about some security problems I've uncovered in Windows 95/98/NT,
Office 95/97, and Outlook. It's critically important that you protect your
system against these attacks.  Visit these sites for more information..."
The rest of the message contains 42 links to sites about Linux and free
software.

Details on how the virus started are a bit sketchy.  The "Anonymous
Longhair" who created it only posted it to Usenet as an early April Fool's
gag, demonstrating how easy it would be to mount a "Linux revolution".
The War Against Linux

A significant obstacle on the path to Linux World Domination has emerged.  A
reactionary grass-roots movement has formed to fight, as they call it, "The
War Against Linux".  This movement, code-named "LinSux", is composed of
people (mostly Microsoft stockholders and commercial software developers)
who want to maintain the status quo.  They are fighting back against the
rise of Linux and free software which they see as a threat to their financial
independence.

The most damaging attack the LinSux folks have launched is "Three Mile
Island", a Windows macro virus designed to inflict damage on computers that
contain a partition devoted to a non-Microsoft OS.  When the victim computer
is booted into Windows, the virus activates and deletes any non-Microsoft
partitions. Ironically, the many security flaws in Windows allow the virus
to damage alternative operating systems but leave Windows unscathed.

"The War Against Linux" has also been fought in more subtle ways.
Time-tested methods of Linux advocacy have been turned into subtle forms of
anti-Linux advocacy by the LinSux crowd.  MSCEs are smuggling NT boxes into
companies that predominantly use Linux or Unix.  LinSux "freedom fighters"
are rearranging books and software boxes on store shelves so that Microsoft
offerings are displayed more prominently.
Actual Snippet of Windows Source Code!  Honest!

NOTE: The following snippet of the Windows 95 source code was sent to us via
'unofficial' channels.  Don't tell anyone you saw this!  We really don't
feel like being visited by the Microsoft Intellectual Property Police.

void BusyLoop()
/* Do nothing loop to kill CPU cycles; added at the
   request of Intel */
{
DisplayRandomSubliminalMessage();
for( int i = 0; i < BIG_INT; i++ )
  for( int j = 0; j < BIG_INT; j++ )
   for( int k = 0; k < BIG_INT; k++ )
    for( int l = 0; l < BIG_INT; l++ )
     if( STACK_SPACE_PERCENTAGE_FREE > .05 )
     /* There's plenty of stack space left -- let's
        eat up some more CPU cycles, recursively! */
      BusyLoop();
}
Microsoft Mandatory Survey (#13)

Customers who want to upgrade to Windows 98 Second Edition must now fill
out a Microsoft survey online before they can order the bugfix/upgrade.

Question 13: Which of the following new Microsoft products do you plan on
             buying within the next 6 months?

A. Windows For Babies(tm) - Using an enhanced "click-n-drool" interface,
   babies will be able to learn how to use a Wintel computer, giving them
   a head start in living in a Microsoft-led world.

B. Where In Redmond Is Carmen Sandiego?(tm) - The archvillian Sandiego has
   stolen the Windows source code and must be stopped before she can
   publish it on the Net.

C. ActiveKeyboard 2000(tm) - An ergonomic keyboard that replaces useless
   keys like SysRq and Scroll Lock with handy keys like "Play Solitaire"
   and "Visit Microsoft.com".

D. Visual BatchFile(tm) - An IDE and compiler for the MS-DOS batch file
   language. MSNBC calls it "better than Perl".
Linux World Domination: Not A Joke!

WASHINGTON, D.C. -- Senator Fattecat (R-WA) is pushing for a ban on
Finnish-produced software. His chief of staff, Ms. Dee Septive, has
published a 200-page report revealing "the Helsinkian Underground", a
Finnish world domination plot hatched in 1943.

The Fattecat expose describes Finland's recent scheme involving free
software. "Linux, originally called Freix (FREIX Retrieves Electronic
Intelligence X), is a scheme to infiltrate the Western world with a 'free'
operating system with nasty backdoors hidden within its obfuscated source
code. IRC (Intelligence Relaying Code) is another Finnish innovation
designed for spying purposes."

Linus Torvalds plays a prominent role in the conspiracy. "That old story
about Linus developing a Unix clone in his spare time while at University
is a lark," the report states. "Indeed, the name Linux ("Line X") was
coined because the kernel can extract any arbitrary line of intelligence
from any document it has access to."
New Linux Companies Hope To Get Rich Quick (#1)

Adopt-A-Beowulf: the latest company to hop the Linux bandwagon
as it tramples down Wall Street.

Every geek dreams of owning their own Beowulf supercomputer. Very few
people (except for dotcom billionnaires) can afford to build one, but the
folks at Adopt-a-Beowulf can provide the next best thing: a virtual
beowulf. For US$49.95, you can "adopt" your own 256-node Beowulf cluster.
You won't own it, or even get to see it in person, but you will receive
photos of the cluster, a monthly newsletter about its operation, and a
limited shell account on it.

The company hopes to branch out into other fields. Some slated products
include Adopt-A-Penguin, Lease-A-Camel (for Perl mongers), and
Adopt-A-Distro (in which your name will be used as the code-name for a
beta release of a major Linux distribution or other Open Source project).
The new "I Love You" virus is not the work of some snot-nosed acne-laced
teenager working from a basement in the Phillipines. It's actually part of
a conspiracy concocted by the unholy alliance of Microsoft and several
well-known and well-despised spammers.

You'll notice that the ILOVEYOU, Melissa, and Tuxissa strains all extract
email addresses from the victim's system. This is a gold mine for
spammers, who are able to use these viruses to harvest active email
addresses for them. Everytime ILOVEYOU, for instance, propogates, it keeps
track of all the email addresses it has been sent to, so that when it
finally boomerangs back to a spammer, they have a nice convenient list of
addresses to send "laser printer toner" and "get rich quick!"
advertisements to.

   -- Bob Smith (not his real code-name), in a speech given at the
      First Annual Connecticut Conspiracy Convention (ConConCon),
      "the largest ever gathering of conspiracy theorists east of the
      Mississippi."
Security Holes Found In Microsoft Easter Eggs

REDMOND, WA -- It's damage control time for the Microsoft Marketing
Machine. Not only have exploits been found in IE, Outlook, and even the
Dancing Paper Clip, but now holes have been uncovered in Excel's Flight
Simulator and Word's pinball game.

"If you enter Excel 97's flight simulator and then hit the F1, X, and
SysRq keys while reading a file from Drive A:, you automatically gain
Administrator rights on Windows NT," explained the security expert who
first discovered the problem. "And that's just the tip of the iceberg."

Office 97 and 2000 both contain two hidden DLLs, billrulez.dll and
eastereggs.dll, that are marked as "Safe for scripting" but are not.
Arbitrary Visual BASIC code can be executed using these files. More
disturbing, however, are the undocumented API calls
"ChangeAllPasswordsToDefault", "OpenBackDoor", "InitiateBlueScreenNow",
and "UploadRegistryToMicrosoft" within easter~1.dll.

Microsoft spokesdroids have already hailed the problem as "an
insignificant byproduct of Microsoft innovation."
Brief History Of Linux (#2)
Hammurabi's Open-Source Code

Hammurabi became king of Babylonia around 1750BC. Under his reign, a
sophisticated legal code developed; Version 1, containing 282 clauses, was
carved into a large rock column open to the public. However, the code
contained several errors (Hammurabi must have been drunk), which numerous
citizens demanded be fixed.

One particularly brave Babylonian submitted to the king's court a stack of
cloth patches that, when affixed to the column, would cover up and correct
the errors. With the king's approval, these patches were applied to the
legal code; within a month a new corrected rock column (Version 2.0) was
officially announced. While future kings never embraced this idea (who
wanted to admit they made a mistake?), the concept of submitting patches
to fix problems is now taken for granted in modern times.
Brief History Of Linux (#10)
The AnyQuack Computer

One electronic machine, Colossus, was used by the British in World War II
to decode Nazi transmissions. The code-breakers were quite successful in
their mission, except for the tiny detail that nobody knew how to read
German. They had decoded unreadable messages into... unreadable messages.

Two years later in 1945, a group of professors and students at the Univ.
of Pennsylvania were discussing computing theory. An argument ensued, in
which one professor yelled, "Any quack can build an electronic computer!
The real challenge is building one that doesn't crash every five minutes."

One graduate student, J. Presper Eckert, Jr., responded, "I'm any quack!
I'll take you up on that challenge. I'll build a device that can calculate
1,000 digits of pi in one hour... without crashing!" Several professors
laughed; "Such high-speed calculations are beyond our level of technology."

Eckert and his friends did build such a device. As a joke, he called the
machine "AnyQuack", which eventually became ENIAC -- ENIAC's Not Intended
As Crashware, the first known example of a self-referential acronym.
Brief History Of Linux (#13)
Wanted: Eunuchs programmers

Everything you know about the creation of the Unix operating system is
wrong. We have uncovered the truth: Unix was a conspiracy hatched by
Ritchie and Thompson to thwart the AT&T monopoly that they worked for. The
system, code-named EUNUCHS (Electronic UNtrustworthy User-Condemning
Horrible System), was horribly conceived, just as they had planned.

The OS, quickly renamed to a more respectable "Unix", was adopted first by
Ma Bell's Patent Department and then by the rest of the monopoly. AT&T saw
an inexpensive, multi-user, portable operating system that it had all
rights to; the authors, however, saw a horrible, multi-crashing system
that the Evil Ma Bell Empire would become hopelessly dependent on. AT&T
would go bankrupt trying to maintain the system and eventually collapse.

That didn't happen. Ritchie and Thompson were too talented to create a
crappy operating system; no matter how hard they tried the system was too
good. Their last ditch effort to sabotage the system by recoding it
obfuscated C was unsuccessful. Before long Unix spread outside of Bell
Labs and their conspiracy collapsed.
Brief History Of Linux (#17)
If only Gary had been sober

When Micro-soft moved to Seattle in 1979, most of its revenue came from
sales of BASIC, a horrible language so dependant on GOTOs that spaghetti
looked more orderly than its code did. (BASIC has ruined more promising
programmers than anything else, prompting its original inventor Dartmouth
University to issue a public apology in 1986.)

However, by 1981 BASIC hit the backburner to what is now considered the
luckiest break in the history of computing: MS-DOS. (We use the term
"break" because MS-DOS was and always will be broken.) IBM was developing
a 16-bit "personal computer" and desperately needed an OS to drive it.

Their first choice was Gary Kildall's CP/M, but IBM never struck a deal
with him. We've discovered the true reason: Kildall was drunk at the time
the IBM representatives went to talk with him. A sober man would not have
insulted the reps, calling their employer an "Incredibly Bad Monopoly" and
referring to their new IBM-PC as an "Idealistically Backwards
Microcomputer for People without Clues". Needless to say, Gary "I Lost The
Deal Of The Century" Kildall was not sober.
Brief History Of Linux (#17)
Terrible calamity

IBM chose Microsoft's Quick & Dirty Operating System instead of CP/M for
its new line of PCs. QDOS (along with the abomination known as EDLIN) had
been acquired from a Seattle man, Tim Paterson, for the paltry sum of
$50,000. "Quick" and "Dirty" were truly an accurate description of this
system, because IBM's quality assurance department discovered 300 bugs in
QDOS's 8,000 lines of assember code (that's about 1 bug per 27 lines --
which, at the time, was appalling, but compared with Windows 98 today, it
really wasn't that shabby).

Thanks in part to IBM's new marketing slogan, "Nobody Ever Got Fired For
Choosing IBM(tm)", and the release of the VisiCalc spreadsheet program
that everybody and their brother wanted, IBM PCs running DOS flew off the
shelves and, unfortunately, secured Microsoft's runaway success. Bill
Gates was now on his way to the Billionaire's Club; his days as a mediocre
programmer were long gone: he was now a Suit. The only lines of code he
would ever see would be the passcodes to his Swiss bank accounts.
Brief History Of Linux (#21)
The GNU Project

Meet Richard M. Stallman, an MIT hacker who would found the GNU Project
and create Emacs, the operating-system-disguised-as-a-text-editor. RMS,
the first member of the Three Initials Club (joined by ESR and JWZ),
experienced such frustration with software wrapped in arcane license
agreements that he embarked on the GNU Project to produce free software.

His journey began when he noticed this fine print for a printer driver:

   You do not own this software. You own a license to use one copy of this
   software, a license that we can revoke at any time for any reason
   whatsoever without a refund. You may not copy, distribute, alter,
   disassemble, or hack the software. The source code is locked away in a
   vault in Cleveland. If you say anything negative about this software
   you will be in violation of this license and required to forfeit your
   soul and/or first born child to us.

The harsh wording of the license shocked RMS. The computer industry was in
it's infancy, which could only mean it was going to get much, much worse.
Brief History Of Linux (#23)

Linus Torvalds certainly wasn't the only person to create their own
operating system from scratch. Other people working from their leaky
basements did create their own systems and now they are sick that they
didn't become an Alpha Geek like Torvalds or a Beta Geek like Alan Cox.

Linus had one advantage not many else did: Internet access. The world was
full of half-implemented-Unix-kernels at the time, but they were sitting
isolated on some hacker's hard drive, destined to be destroyed by a hard
drive crash. Thankfully that never happened to Linux, mostly because
everyone with Net access could download a copy instead of paying shipping
charges to receive the code on a huge stack of unreliable floppy disks.

Indeed, buried deep within a landfill in Lansing, Michigan sits a stack of
still-readable 5-1/4 floppies containing the only known copy of "Windows
Killer", a fully functional Unix kernel so elegant, so efficient, so
easy-to-use that Ken Thompson himself would be jealous of its design.
Unfortunately the author's mother threw out the stack of floppies in a
bout of spring cleaning. The 14 year old author's talents were lost
forever as his parents sent him to Law School.
Brief History Of Linux (#26)

On the surface, Transmeta was a secretive startup that hired Linus
Torvalds in 1996 as their Alpha Geek to help develop some kind of
microprocessor. Linus, everyone found out later, was actually hired as
part of a low-budget yet high-yield publicity stunt. While other dotcoms
were burning millions on glitzy marketing campaigns nobody remembers and
Superbowl ads displayed while jocks went to the bathroom, Transmeta was
spending only pocket change on marketing. Most of that pocket change went
towards hosting the Transmeta website (the one that wasn't there yet)
which, incidentally, contained more original content and received more
visitors than the typical dotcom portal.

Microsoft relies on vaporware and certain ahem stipends given to
journalists in order to generate buzz and hype for new products, but
Transmeta only needed Non-Disclosure Agreements and the Personality Cult
of Linus to build up its buzz. When the secret was finally unveiled, the
Slashdot crowd was all excited about low-power mobile processors and
code-morphing algorithms -- for a couple days. Then everyone yawned and
went back to playing Quake. It's still not entirely clear when Transmeta
is actually supposed to start selling something.
Brief History Of Linux (#29)

"The Cathedral and the Bazaar" is credited by many (especially ESR
himself) as the reason Netscape announced January 22, 1998 the release of
the Mozilla source code. In addition, Rob Malda of Slashdot has also
received praise because he had recently published an editorial ("Give us
the damn source code so we can fix Netscape's problems ourselves!")

Of course, historians now know the true reason behind the landmark
decision: Netscape engineers were scared to death that a large
multi-national corporation would acquire them and crush Mozilla. Which
indeed did happen much later, although everybody thought the conqueror
would be Microsoft, not AOL (America's Online Lusers).

The Netscape announcement prompted a strategy session among Linux bigwigs
on February 3rd. They decided a new term to replace 'free software' was
needed; some rejected suggestions included "Free Source", "Ajar Source",
"World Domination Source", "bong-ware" (Bong's Obviously Not GNU), and
"Nude Source". We can thank Chris Peterson for coining "Open Source",
which became the adopted term and later sparked the ugly "Free Software
vs. Open Source", "Raymond vs. Stallman" flame-a-thons.
/*
* Hi, this is Linus Torvalds speaking, your Benevolent Dictator. I'm typing
* this today to talk about EyeOpener(tm) brand caffeinated beverages, for
* those really, really, _really_ long nights of kernel hacking.
*
* EyeOpener(tm): When ordinary colas don't keep you awake for 72 hours
* straight.
*/

   -- Comment embedded in Linux kernel 2.6.15 after Linus Torvalds
      decided to get-rich-quick by placing "comment-verts" in the code
DeCSS T-Shirt Used To Commit Piracy!

College student Cody Potter stunned the world yesterday when he used a
T-shirt with the printed DeCSS source code to illegally copy a DVD of
"Star Trek XXI: We Promise This Is The Last One". Well, it wasn't the
actual DeCSS source code. The shirt contained a Perl script which spits
out a bash shell script which produces a GW-BASIC program which outputs a
ROT13-encoded Python script that manufactures a Pig-Latin-encoded Java
program that finally produces the real DeCSS C source code when executed.
Unobfuscated Perl (#1)

A rogue group of Perl hackers has presented a plan to add a "use
really_goddamn_strict" pragma that would enforce readability and
UNobfuscation. With this pragma in force, the Perl compiler might say:

* Warning: Program contains zero comments. You've probably never seen or
  used one before; they begin with a # symbol. Please start using them or
  else a representative from the nearest Perl Mongers group will come to
  your house and beat you over the head with a cluestick.

* Warning: Program uses a cute trick at line 125 that might make sense in
  C. But this isn't C!

* Warning: Code at line 412 indicates that programmer is an idiot. Please
  correct error between chair and monitor.

* Warning: While There's More Than One Way To Do It, your method at line
  523 is particularly stupid. Please try again.
Unobfuscated Perl (#2)

A rogue group of Perl hackers has presented a plan to add a "use
really_goddamn_strict" pragma that would enforce readability and
UNobfuscation. With this pragma in force, the Perl compiler might say:

* Warning: Write-only code detected between lines 612 and 734. While this
  code is perfectly legal, you won't have any clue what it does in two
  weeks. I recommend you start over.

* Warning: Code at line 1,024 is indistinguishable from line noise or the
  output of /dev/random

* Warning: Have you ever properly indented a piece of code in your entire
  life? Evidently not.

* Warning: I think you can come up with a more descriptive variable name than
  "foo" at line 1,523.

* Warning: Programmer attempting to re-invent the wheel at line 2,231.
  There's a function that does the exact same thing on CPAN -- and it
  actually works.
UNobfuscated Perl Code Contest

The Perl Gazette has announced the winners in the First Annual Unobfuscated
Perl Code Contest. First place went to Edwin Fuller, who submitted this
unobfuscated program:

  #!/usr/bin/perl
  print "Hello world!\n";

"This was definitely a challenging contest," said an ecstatic Edwin
Fuller. "I've never written a Perl program before that didn't have
hundreds of qw( $ @ % & * | ? / \ ! # ~ ) symbols. I really had to summon
all of my programming skills to produce an unobfuscated program."

...The second place winner, Mrs. Sea Pearl, submitted the following code:

  #!/usr/bin/perl
  use strict;
  # Do nothing, successfully
  exit(0);
"Oops," Says MPAA President

Recently, the United States filed a legal brief in support of the MPAA's
argument that linking to the DeCSS source code is not protected by the
First Amendment.

At the time, the MPAA was ecstatic. But not any longer. The tables have
turned: the Federal government has filed a lawsuit against the movie
industry, arguing that many Hollywood-produced movies 'link' to illegal
content. The MPAA is now desperately wrapping itself up in the Bill of
Rights.

"Murder is illegal. Showing a murder in a movie -- or, rather, 'linking'
to it -- is also illegal," explained a spokesperson for the Coalition Of
Angry Soccer Moms In Support Of Brow-Beating Movie Industry Executives, an
interest group that has backed the government's lawsuit.
As Easy As /usr/src/linux

Wiping the sweat from his brow, the contestant diligently continues to
recite, "'i' equals 'NR' underscore 'TASKS' semicolon newline 'p' equals
ampersand 'task' bracket 'NR' underscore 'TASKS' close-bracket semicolon
newline while parens minus minus 'i' parens brace if parens star minus..."

Bzzzt! One of the judges says, "You missed an exclamation point. Ten point
penalty for that error."  The contestant realizes it's all over. He had
spent 500 hours memorizing the source code to the Linux 0.01 kernel and
then blew it all by forgetting one stupid ASCII character in sched.c.

Welcome to the First Annual Linux Kernel Memorization Contest in New
Haven, Connecticut, where the stakes are high and the frustration is
simply unbearable. Linuxer longhairs from all over the globe have
descended on the Offramp Motel to show off their memorization skills in
front of a crowd of... dozens.

"Those math freaks can memorize PI and other irrational constants all they
want. I'll stick with the Linux 0.01 kernel source code thank you very
much," said Bob Notmyrealname, the organizer of the event. %
"And I doubt complaining to the author gets you anything but a free procmail
rule."

        - Alan Cox on asking authors to document their code
"Talk is cheap. Show me the code."

        - Linus Torvalds
"Linux kernel development is dominated by a hacker ethos, in which
external documentation is held in contempt, and even code comments
are viewed with suspicion."

         - Jerry Epplin
/me thinks ext2 code is more effectively encrypted than DVDs are ;)

        - Andrew Ebling on #kernelnewbies
I can see the intent.

I can also see that the code doesn't match up to the intent.

I call that a bug. You don't. Fine.

        - Linus Torvalds rejecting a patch on linux-kernel
It should be fixed, but it won't be easy and it won't be fast. If you want
to help - wonderful. But keep in mind that it will take months of wading
through the ugliest code we have in the tree. If you've got a weak stomach -
stay out. I've been there and it's not a nice place.

        - Al Viro on fixing drivers
Sorry about the rant - I've just spent a couple of hours wading through
the piles of excrements in drivers/*. Ouch.

        - Al Viro about ugly code in device drivers on linux-kernel
Code like that would not pass through anybody's yuck-o-meter.

        - Linus Torvalds about design on linux-kernel
... and for absolute majority of programmers additional shared objects mean
additional fsckup sources.  I don't trust them to write correct async code.
OK, so I don't trust the majority of programmers to find their dicks if
you take their Visual Masturbation Aid++ away, but that's another story -
I'm talking about otherwise clued people, not burger-flippers armed with
Foo For Complete Dummies in 24 Hours.

        - Al Viro about multi-threading on linux-kernel
The fact that it takes more code to parse and interpret ACPI than it does to
route traffic on the internet backbones should be a hint something is badly
wrong either in ACPI the spec, ACPI the implenentation or both.

        - Alan Cox on linux-kernel
  If you really want to know where you stand, it'll cost you around
  $15K and that, in my opinion, is fine. If it isn't worth $15K to
  protect your code then it is worth so little to you that there really
  is no good reason not to just GPL it from the start.

        - Larry McVoy on GPL licensing issues
Would you like to code up this, test it and send it to me?

Btw, good debugging!

                Linus "lazy is my middle name" Torvalds
With the current ACPI code in my test boxes it seems to be no worse than
APM, unfortunately it would be hard to be worse.

        - Alan Cox on the ACPI mailing list
        When devfs went into the tree, the word was "at least it will
make people look at the code".  Well, it did.  Veni, vidi, vomere.

        - Al Viro on linux-kernel
> ...  but i could not found any source code or
> information in Internet.

How strange. The kernel source code is definitely on the internet, and
definitely contains drivers that implement internal layering -
nrdev, shaper, the sync cards, isdn

        - Alan Cox on linux-kernel
> Sorry, at this point we are not allowed to publish the source code of the
> lcs and qeth drivers (due to the use of confidential hardware interface
> specifications).  We make those modules available only in binary form
> on our developerWorks web site.
>
Gosh. I didn't know you guys were so advanced that you didn't use
an electronic hardware interface! Your 'hardware interface specifications'
use magnetohydrodynamics, and they are top-secret, right?

        - Richard B. Johnson on linux-kernel
/*
*  Check for clue free BIOS implementations who use
*  the following QA technique
*
*      [ Write BIOS Code ]<------
*               |                ^
*      < Does it Compile >----N--
*               |Y               ^
*      < Does it Boot Win98 >-N--
*               |Y
*           [Ship It]
*
*/

        - comment from arch/i386/kernel/dmi_scan.c
Interface definitions tend to be treated a little differently to "code". But
as I keep trying to beat into people - if you are going to mix GPL and non
GPL code see a lawyer - thats what they are there for

        - Alan Cox on linux-kernel
indent does _not_ solve the problem of:
        * buggers who use typedefs like WORD, DWORD, BYTE, IMANIDIOTSHOOTME
        and other crap from the same source (OK, they don't write the last one
        explicitly - not that it wasn't obvious from the rest of their,
        ahem, code).

        - Alexander Viro on coding style
Alexander Viro wrote:
> Al, -><- close to setting up a Linux Kernel Hall of Shame - one with names of
> wankers (both individual and coprorat ones) responsible, their code and
> commentary on said code...

Please, please, please, I'm begging you, please do this.  It's the only way
people learn quickly.  Being nice is great, but nothing works faster than
a cold shower of public humiliation :-)

        - Larry McVoy on linux-kernel
We need to teach Linus about "taste" in drivers. His core code taste is
impeccable, but I'm not fond of his driver taste ;)

        - Alan Cox on linux-kernel
"This is the element_data structure for elements whose *element_type =
FORM_TYPE_SELECT_ONE, FORM_TYPE_SELECT_MULT. */ /* * nesting deeper
and deeper, harder and harder, go, go, oh, OH, OHHHHH!! * Sorry, got
carried away there. */ struct lo_FormElementOptionData_struct."
        -- Mozilla source code
<Overfiend> Don't come crying to me about your "30 minute compiles"!!  I
            have to build X uphill both ways!  In the snow!  With bare
            feet! And we didn't have compilers!  We had to translate the
            C code to mnemonics OURSELVES!
<Overfiend> And I was 18 before we even had assemblers!
<zarkov> "NT 5.0.  All the bugs and ten times the code size!"
<dark> "Yes, your honour, I have RSA encryption code tattood on my
        penis.  Shall I show the jury?"
// Minor lesson: don't fuck about with something you don't fully understand
        -- the dosdoom source code
Operating Systems Installed:
  * Debian GNU/Linux 2.1 4 CD Set ($20 from www.chguy.net; price includes
    taxes, shipping, and a $3 donation to FSF). 2 CDs are binaries, 2 CDs
    complete source code;
  * Windows 98 Second Edition Upgrade Version ($136 through Megadepot.com,
    price does not include taxes/shipping). Surprisingly, no source code
    is included.

        -- Bill Stilwell, http://linuxtoday.com/stories/8794.html
<Knghtbrd> the problem with the GNU coding standards is they ASSUME that
           everyone in the world uses emacs..  If that were the case, free
           software would die because we would all have wrist problems
           like RMS by now and no longer be able to code.  ;>
I would rather spend 10 hours reading someone else's source code than 10
minutes listening to Musak waiting for technical support which isn't.
        -- Dr. Greg Wettstein, Roger Maris Cancer Center
<raptor> Adamel, i think the code you fixed of mine didn't work
<raptor> i must not have commited the working code
<Knghtbrd> raptor: like it's the first time THAT has ever happened  =p
<Deek> you GPL your homework? :)
<knghtbrd> yah  =D
<knghtbrd> Anyone is permitted to use or modify my homework, but if they
           distribute changes they must include the full machine-readable
           source code ;>
* joeyh_ runs ps and sees 10 lines of awk code
* joeyh_ recoils in horror
It's not usually cost effective time wise to go do it. But if something's
really pissing you off, you just go find the code and fix it and that's
really cool.
        -- John Carmack, on the advantages of open source
<taniwha> Knghtbrd: we should do a quake episode :knee deep in the code":
          you run around shooting at bugs:)
<Knghtbrd> taniwha: I'll pass the idea on to OpenQuartz  ;>
* Dry-ice can't code his way out of a paper bag
<Coderjoe> dry-ice: int main() { ExitPaperBag(); return 0; }
<Knghtbrd> Is that how that's done then?  *takes notes*
Nothing is a problem once you debug the code.
        -- John Carmack
We reject: kings, presidents, and voting.
We believe in: rough consensus and working code.
        -- Dave Clark
99 little bugs in the code, 99 bugs in the code,
        fix one bug, compile it again...
        101 little bugs in the code....
<NullC> I like the seed code for computing masking curves.
<NullC> I've never seen code that made be want to drink before that...
<WildCode> Mercury, isn't debugging X a little like finding perfectly
           bugfree code in windows ??
<Mercury> WildCode: Debugging X is like trying to run a straight line
          through a maze.
<Mercury> You just need to bend space-time so that the corners move around
          you and you won't have any problems. (=:]
* Equivalent code is available from RSA Data Security, Inc.
* This code has been tested against that, and is equivalent,
* except that you don't need to include two pages of legalese
* with every copy.
        -- public domain MD5 source
Never underestimate the power of somebody with source code, a text editor,
and the willingness to totally hose their system.
        -- Rob Landley <telomerase@yahoo.com>
<wli> Yeah, I looked at esd and it looked like the kind of C code that an
      ex-JOVIAL/Algol '60 coder who had spent the last 20 years bouncing
      between Fortran-IV and Fortran '77 would write.
<calc> Knghtbrd: irc doesn't compile c code very well ;)
<|Rain|> with sane code, maybe I could figure out the renderer :)
<LordHavoc> rain: I'd probably be the one writing the renderer
<|Rain|> well, er, uh
<Knghtbrd> I'd better put the incriminating stuff into code:  ahfuiovka
           ikperoa edfr ade 9 enbuw ejasxleme ka iena df4mesa
<Knghtbrd> If you can decrypt that, you're a better cryptographer than I
           am.  =)
<Knghtbrd> "... you will more than likely see all kinds of compiler
           warnings scrolling by on the screen. These are normal and can
           be safely ignored."
<LordHavoc> Knghtbrd: is that a note attached to some M$ code?
<Knghtbrd> No, it's a note about a bunch of GNU stuff.
I would rather spend 10 hours reading someone else's source code than
10 minutes listening to Musak waiting for technical support which isn't.
        -- Dr. Greg Wettstein, Roger Maris Cancer Center
We use Linux for all our mission-critical applications.  Having the source code
means that we are not held hostage by anyone's support department.
        -- Russell Nelson, President of Crynwr Software
Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of
code using nothing but vi or emacs.  AAAAACK!
        -- Discussion on the intuitiveness of commands, especially Emacs
Besides, its really not worthwhile to use more than two times your physical
ram in swap (except in a select few situations). The performance of the system
becomes so abysmal you'd rather heat pins under your toenails while reciting
Windows95 source code and staring at porn flicks of Bob Dole than actually try
to type something.
        -- seen on c.o.l.development.system, about the size of the swap space
Also another major deciding factor is availability of source code.
It just gives everybody a warm fuzzy feeling knowing that there is
source code available to the product you are using.  It allows everybody
to improve on the product and fix bugs etc. sooner that the author(s)
would get the time/chance to.
        -- Atif Khan
> Also another major deciding factor is availability of source code.
> It just gives everybody a warm fuzzy feeling knowing that there is
> source code available to the product you are using.  It allows everybody
> to improve on the product and fix bugs etc. sooner that the author(s)
> would get the time/chance to.

I think this is one the really BIG reasons for the snowball/onslaught
of Linux and the wealth of stuff available that gets enhanced faster
than the real vendors can keep up.
        -- Norman
When you have 200 programmers trying to write code for one
product, like Win95 or NT, what you get is a multipule personality
program.  By definition, the real problem is that these programs are
psychotic by nature and make people crazy when they use them.
        -- Joan Brewer on alt.destroy.microsoft
<dark> Turns out that grep returns error code 1 when there are no matches.
       I KNEW that.  Why did it take me half an hour?
        -- Seen on #Debian
/* And you'll never guess what the dog had */
/*   in its mouth... */
             -- Larry Wall in stab.c from the perl source code
break;                          /* don't do magic till later */
             -- Larry Wall in stab.c from the perl source code
/* dbmrefcnt--;  */     /* doesn't work, rats */
             -- Larry Wall in hash.c from the perl source code
#define NULL 0           /* silly thing is, we don't even use this */
             -- Larry Wall in perl.c from the perl source code
#define SIGILL 6         /* blech */
             -- Larry Wall in perl.c from the perl source code
double value;                /* or your money back! */
short changed;               /* so triple your money back! */
             -- Larry Wall in cons.c from the perl source code
#else /* !STDSTDIO */     /* The big, slow, and stupid way */
             -- Larry Wall in str.c from the perl source code
Even if you aren't in doubt, consider the mental welfare of the person who
has to maintain the code after you, and who will probably put parens in
the wrong place.  -- Larry Wall in the perl man page
if (instr(buf,sys_errlist[errno]))  /* you don't see this */
             -- Larry Wall in eval.c from the perl source code
if (rsfp = mypopen("/bin/mail root","w")) {     /* heh, heh */
             -- Larry Wall in perl.c from the perl source code
It won't be covered in the book.  The source code has to be useful for
something, after all...  :-)
             -- Larry Wall in <10160@jpl-devvax.JPL.NASA.GOV>
/* now make a new head in the exact same spot */
             -- Larry Wall in cons.c from the perl source code
pos += screamnext[pos]  /* does this goof up anywhere? */
             -- Larry Wall in util.c from the perl source code
Real programmers can write assembly code in any language.   :-)
             -- Larry Wall in  <8571@jpl-devvax.JPL.NASA.GOV>
s = (char*)(long)retval;                /* ouch */
             -- Larry Wall in doio.c from the perl source code
signal(i, SIG_DFL); /* crunch, crunch, crunch */
             -- Larry Wall in doarg.c from the perl source code
stab_val(stab)->str_nok = 1;    /* what a wonderful hack! */
             -- Larry Wall in stab.c from the perl source code
str->str_pok |= SP_FBM;                     /* deep magic */
s = (unsigned char*)(str->str_ptr);         /* deeper magic */
             -- Larry Wall in util.c from the perl source code
/* This bit of chicanery makes a unary function followed by
a parenthesis into a function with one argument, highest precedence. */
             -- Larry Wall in toke.c from the perl source code
tmps_base = tmps_max;                /* protect our mortal string */
             -- Larry Wall in stab.c from the perl source code
/* we have tried to make this normal case as abnormal as possible */
             -- Larry Wall in cmd.c from the perl source code
(Presuming for the sake of argument that it's even *possible* to design
better code in Perl than in C.  :-)
    -- Larry Wall on core code vs. module code design
The code also assumes that it's difficult to misspell "a" or "b".  :-)
             -- Larry Wall in <199710221731.KAA24396@wall.org>
It's hard to tune heavily tuned code.  :-)
             -- Larry Wall in <199801141725.JAA07555@wall.org>
My CODE of ETHICS is vacationing at famed SCHROON LAKE in upstate New York!!
World War Three can be averted by adherence to a strictly enforced dress code!
A CODE OF ETHICAL BEHAVIOR FOR PATIENTS:

1. DO NOT EXPECT YOUR DOCTOR TO SHARE YOUR DISCOMFORT.
        Involvement with the patient's suffering might cause him to lose
        valuable scientific objectivity.

2. BE CHEERFUL AT ALL TIMES.
        Your doctor leads a busy and trying life and requires all the
        gentleness and reassurance he can get.

3. TRY TO SUFFER FROM THE DISEASE FOR WHICH YOU ARE BEING TREATED.
        Remember that your doctor has a professional reputation to uphold.
A CODE OF ETHICAL BEHAVIOR FOR PATIENTS:

4. DO NOT COMPLAIN IF THE TREATMENT FAILS TO BRING RELIEF.
        You must believe that your doctor has achieved a deep insight into
        the true nature of your illness, which transcends any mere permanent
        disability you may have experienced.

5. NEVER ASK YOUR DOCTOR TO EXPLAIN WHAT HE IS DOING OR WHY HE IS DOING IT.
        It is presumptuous to assume that such profound matters could be
        explained in terms that you would understand.

6. SUBMIT TO NOVEL EXPERIMANTAL TREATMENT READILY.
        Though the surgery may not benefit you directly, the resulting
        research paper will surely be of widespread interest.
A CODE OF ETHICAL BEHAVIOR FOR PATIENTS:

7. PAY YOUR MEDICAL BILLS PROMPTLY AND WILLINGLY.
        You should consider it a privilege to contribute, however modestly,
        to the well-being of physicians and other humanitarians.

8. DO NOT SUFFER FROM AILMENTS THAT YOU CANNOT AFFORD.
        It is sheer arrogance to contract illnesses that are beyond your means.

9. NEVER REVEAL ANY OF THE SHORTCOMINGS THAT HAVE COME TO LIGHT IN THE COURSE
   OF TREATMENT BY YOUR DOCTOR.
        The patient-doctor relationship is a privileged one, and you have a
        sacred duty to protect him from exposure.

10. NEVER DIE WHILE IN YOUR DOCTOR'S PRESENCE OR UNDER HIS DIRECT CARE.
        This will only cause him needless inconvenience and embarrassment.
No guarantee of accuracy or completeness!
©TU Chemnitz, 2006-2024
Your feedback:
Ad partners