lkml.org 
[lkml]   [1999]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: Profanity in the Linux Kernel?!?!?

On 8 Jun 1999, Scott Jaderholm wrote:

> It seems to me that if you are trying to make an OS that is going to be
> used by the masses you would try and present yourselves as best as
> possible. Using profanity to document your code doesn't seem all that
> appealing to me, but I don't know about others.

> Is it really necessary? Someone could easily put "messed up" in place
> of it.

Someone else brought up the point about censoring work other people
contributed, and I agree with that. I have absolutely no problem
with a developer calling a spade a spade.

However. For those with delicate sensibilities, I present a humble
patch made against the 2.2.9 kernel source. It merely adds a make
rule that calls a fairly lame shell script to replace the naughty
words with something a little more Donna Reed.

Chance that it breaks something important: high
Chance that it catches all the bad words : low

But it should be enough to get you started on leading the project
to wash out the kernel source's mouth with soap.

cp repent.patch /usr/src/linux
cd /usr/src/linux
patch -p1 < repent.patch

make repent

And rest easy knowing that you're one of the elite few who are
running a saintly Linux kernel that will probably throw errors
at you left and right as you try to compile it.


Take it easy,

--
Kelley Spoon <kspoon@turbolinux.com>
diff -uNr linux/Makefile linux.repent/Makefile
--- linux/Makefile Wed May 12 08:50:12 1999
+++ linux.repent/Makefile Tue Jun 8 22:19:05 1999
@@ -444,3 +444,17 @@

scripts/split-include: scripts/split-include.c
$(HOSTCC) $(HOSTCFLAGS) -o scripts/split-include scripts/split-include.c
+
+repent: scripts/repent.sh
+ @echo "Ok, weenor. I'll try to clean up the language a bit. However,"
+ @echo "you should probably be aware that some fairly important source"
+ @echo "code might get changed, leaving you with something that won't"
+ @echo "compile."
+ @echo
+ @echo "To add insult to injury, this probably won't catch all the naughty"
+ @echo "words, either. Suck it up and fix the script so that yours will be"
+ @echo "the last set of virgin eyes that ever has to endure the horrors."
+ @echo
+ @echo "I hope having source code you can show your momma was worth it..."
+ @chmod 700 scripts/repent.sh
+ @scripts/repent.sh
diff -uNr linux/scripts/repent.sh linux.repent/scripts/repent.sh
--- linux/scripts/repent.sh Wed Dec 31 16:00:00 1969
+++ linux.repent/scripts/repent.sh Tue Jun 8 22:13:15 1999
@@ -0,0 +1,46 @@
+#!/bin/sh
+
+# If you run this, you are not only a lamer, but
+# fool as well. This will probably break stuff,
+# but if your eternal soul is in jeopardy because
+# you are running an OS with a few very colorful
+# comments in the source, then I guess this is
+# better than nothing.
+
+# K. Spoon
+
+for i in `grep -ri " fuck " ./*|cut -f1 -d:`
+do
+ mv ${i} ${i}.tmp
+ sed 's/[Ff][Uu][Cc][Kk]/[fsck]/g' ${i}.tmp > ${i}
+ rm ${i}.tmp
+done
+
+for i in `grep -ri " damn " ./*|cut -f1 -d:`
+do
+ mv ${i} ${i}.tmp
+ sed 's/[Dd][Aa][Mm][Nn]/[darn]/g' ${i}.tmp > ${i}
+ rm ${i}.tmp
+done
+
+for i in `grep -ri " shit " ./*|cut -f1 -d:`
+do
+ mv ${i} ${i}.tmp
+ sed 's/[Ss][Hh][Ii][Tt]/[shucks]/g' ${i}.tmp > ${i}
+ rm ${i}.tmp
+done
+
+for i in `grep -ri " bitch " ./*|grep -vi bitchange|cut -f1 -d: | grep -v .S`
+do
+ mv ${i} ${i}.tmp
+ sed 's/[Bb][Ii][Tt][Cc][Hh]/*MOAN*/g' ${i}.tmp > ${i}
+ rm ${i}.tmp
+done
+
+for i in `grep -ri " hell " ./* | cut -f1 -d: `
+do
+ mv ${i} ${i}.tmp
+ sed 's/[Hh][Ee][Ll][Ll]/heck/g' ${i}.tmp > ${i}
+ rm ${i}.tmp
+done
+
\
 
 \ /
  Last update: 2005-03-22 13:52    [W:0.208 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site