The Large Hadron Collider: End of the world, or God’s own particle?

Large

Is an understatement. A giant circular tunnel, with several loops, stretches for 27km under the land between France and Switzerland. One of its experimental chambers is bigger than the nave of Westminster Abbey.

Hadron

The name for one of the types of particle that make up an atom. These tiny bits of energy will be propelled by giant magnets around the tunnel circuit at almost the speed of light.

Collide

Is what they will do when they meet other hadrons being beamed in the opposite direction, at the same great speed. The resulting explosion will create 100,000 times more heat than the sun, apparently. Thankfully, it will only happen for a moment, in an area a billion times smaller than a speck of dust.

Nano-Howto to use more than one independent Internet connection.

Nano-Howto to use more than one independent Internet connection.
by Christoph Simon
v1.0, Dec  2, 2001
—————————————————————-

1. Intro
========
1.0 Thanks
———-

The solution presented here is based on the patches by Julian Anastasov. Like several other users on the net struggling with this, I believe they fill in yet another gap for using Linux as a very advanced router. It was hard for me not only to get this running for the first time, but also to understand most of the principles. Also in this Julian has proofed to have unlimited patience. Thanks. He also agreed to expose this file on his site:

            http://www.linuxvirtualserver.org/~julian/nano.txt

How to get out of vi

quoted from http://liw.iki.fi/liw/texts/vi.html For some inexplicable reason people often have trouble getting out of vi, the venerable and mighty UNIX editor. Given that the vi user interface is logical, and therefore easy to learn, this manual should be unnecessary. The world, however, is not what it should be. 22 September…

Linux Anecdotes

quoted from http://liw.iki.fi/liw/texts/linux-anecdotes.html

Linux Anecdotes

A look at the history of Linux, as seen by a long time Linux user. The talk is a series of anecdotes, shy of technical details, and sprinkled with personal memories.

27 April 1998

This talk was given at the 1998 Linux Expo.

Who I am and why I am here

I seem to have acquired a little bit of reputation in the Linux community, despite my efforts in to stay quiet and invisible, so that I don't get so many questions from people having trouble with Linux.

Part of my reputation is that I know Linux pretty well. That part is based on the time when I and Linus Torvalds—I assume you know Linus—shared an office at the University of Helsinki. In reality, I don't know Linux all that well. For example, my one stab at kernel programming resulted in a bug that took three years to track down and fix, and even then it was done by someone hacking OS/2. I'm referring to the sprintf function inside the kernel.

Why Hack Mode Is Better Than Sex

quoted from http://liw.iki.fi/liw/texts/why-hack-mode-is-better-than-sex.html You can do hack mode all day without being called immoral. It's not illegal to get paid for hack mode. It's not embarrassing to read hack mode literature in a train. You don't get diseases from hack mode. Hack mode doesn't result in children. Your computer won't…

Vacations and weekends

quoted from http://liw.iki.fi/liw/texts/vacation.html

Boss, what's vacation?

"Boss, can I ask you something?"

"Sure."

"Everyone's always talking about vacations and free time and things like that. How come I never have any?"

"You wouldn't like it."

"But they think it's better than work. They really look forward to it."

"Remember last year, when the office was shut down for a week."

"When they replaced all windows? Sure I remember. I couldn't play with a computer for a week. Horrible."

"Vacations are like that."

"Oh."

"So you wouldn't like them."

"But everyone else does."

"Ah, but that's because they're lusers, not hackers."

"Oh."

"Now go back and write that compiler. We need it last week."

Important programming truths

quoted from http://liw.fi/programming-truths/

Originally written in 1995.
This page contains a number of important programming truths that every budding programmer should know about. These truths are self-evident, and need no explanations.

If it compiles, it works.
If it compiles, it’s correct.
If it runs, it doesn’t have any bugs.
If it doesn’t have any immediately obvious bugs, it’s perfect.
If a bug doesn’t show, it doesn’t exist.
If it seems to work, it works.
Doing something right is easy. Avoiding errors only takes a bit of concentration.
The shorter the source code, the faster the program.
It’s obvious how to optimize a program.
Prorammers don’t make mistakes.