A closer look at the Linux kernel

Posted by muesli in Tech & Net
Monday, September 22. 2003

Commenting on your source code is one of the pleasures, a developer receives. In the beginning it's a pain in the ***. After a while, you're realising what comments are good for:

1. Giving you hints, extra information and guide others through your code.
2. Make fun of yourself and others.

Examples? Do this:
# cd /usr/src/linux ; egrep -ir "( fuck)|( bullshit)" *

Here are just some of the results:

drivers/scsi/qlogicpti.c: // bullshit
include/linux/netfilter_ipv4/ipt_limit.h: // Ugly, ugly fucker.
fs/binfmt_aout.c: // Fuck me plenty...
drivers/scsi/qlogicpti.h: // Am I fucking pedantic or what?
arch/parisc/kernel/signal.c: // ARGH! Fucking brain damage. You don't want to know.

Funny operating system, I'm using...
muesli

Comments (3) - Trackbacks (0)

Defined tags for this entry: kernel, linux

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

lib/vsprintf.c: * Wirzenius wrote this portably, Torvalds fucked it up

heheheh

#1 Jannis (Homepage) on 2003-09-22 20:39 (Reply)

I choked on my pop and almost gave my monitor a regurgitated Mountain Dew bath upon reading this! ;-] I wonder if I could get away with documenting some of my college assignments this way ;-]

#2 Matthew Jones (Homepage) on 2003-09-22 22:01 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	Enclosing asterisks marks text as bold (word), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information? Subscribe to this entry