lkml.org 
[lkml]   [1999]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Profanity in the Linux Kernel?!?!?
I believe you've missed a couple of the well articulated points; that is that
people are working hard to present Linux as an acceptable component in corporate
environments and that anything which casts a negative impression about the Linux
makes it much harder to fight corporate bean counters that own MicroSloth stock.

This isn't an issue of morals and you should keep your personal slams to
yourself, this is a matter of business and trying to make successful inroads
with powerful tools that we all recognize have value. Childish statements and
actions, or in this case profanity, do nothing but foster an attitude for those
Windoze folks that Linux shouldn't be taken seriously.

Whether you like it or not, there are agendas out there and anything that can
give a product a black-eye will be used to distract or diminish the perceived
quality or viability in a corporate environment.

Barry

Jeff Merkey wrote:

> Who cares! Profanity is like sex, death, and taxes -- it's a part of life.
> Don't you guys have something more constructive to focus on, like getting
> real work done to make Linux better? If folks don't like it, then they
> should join Jerry Falwell's Radio Preacher "moral majority" club or
> something. As swamped as I am with Linux work, I'm surprised folks out
> there have enough idel time on their hands to banter this type of stuff.
>
> Jeff
>
> ----- Original Message -----
> From: Wakko Warner <wakko@animx.eu.org>
> To: Barrett G. Lyon <blyon@netpr.com>; <linux-kernel@vger.rutgers.edu>
> Sent: Wednesday, June 09, 1999 10:37 AM
> Subject: Re: Profanity in the Linux Kernel?!?!?
>
> > > >This topic came up several times before, and the result is that
> > > >arbitrary censorship of code/comments is not going to happen. The
> > > >only exception is in kernel messages which can reach the user in the
> > > >message logs, and those have been cleaned up.
> > >
> > > Not that I care.. but.. :
> > >
> > > ./net/core/profile.c: printk(KERN_CRIT "Yep, guys... our
> template
> > > for proc_*_read is crappy :-)\n");
> > > ./drivers/net/sdladrv.c: printk(KERN_ERR "%s: Damn...
> > > Adapter won't start!\n",
> > > ./drivers/isdn/isdn_common.c: printk(KERN_ERR
> > > "isdn_common: isdn_poll 1 -> what the hell\n");
> > > ./drivers/isdn/isdn_common.c: printk(KERN_ERR "isdn_common: isdn_poll
> 2
> > > -> what the hell\n");
> > > ./arch/sparc64/kernel/traps.c: printk("SHIT[%s:%d]: "
> > > ./arch/sparc64/kernel/traps.c: printk("SHIT[%s:%d]: "
> > > ./arch/sparc64/kernel/traps.c: printk("instruction_access_exception:
> Shit
> > > SFSR[%016lx] SFAR[%016lx], going.\n",
> > > ./arch/sparc64/kernel/traps.c: printk("data_access_exception:
> Shit
> > > SFSR[%016lx] SFAR[%016lx], going.\n",
> >
> > Proposed config option:
> > CONFIG_ENABLE_PROFANITY
> > =)
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.rutgers.edu
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:52    [from the cache]
©2003-2011 Jasper Spaans