os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

By popular request.

Browse source 
For the record, the guilty are <des@freebsd.org> and <eivind@freebsd.org>.
This commit is contained in:
Dag-Erling Smørgrav 1999-04-08 14:36:30 +00:00
parent fad371fe20
commit 525e1f23b0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=4637
1 changed files with 98 additions and 2 deletions

100
FAQ/misc.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: misc.sgml,v 1.15 1999-03-27 15:48:06 nik Exp $ -->
<!-- $Id: misc.sgml,v 1.16 1999-04-08 14:36:30 des Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect>
@ -328,5 +328,101 @@
Systems Research Group) chose for their Unix distribution way
back when.
</sect>
<sect1>
<heading>How many FreeBSD hackers does it take to change a lightbulb?</heading>
<p>One thousand, one hundred and seventy-two:
<p>Twenty-three to complain to -current about the lights being
out;
<p>Four to claim that it is a configuration problem, and that
such matters really belong on -questions;
<p>Three to submit PRs about it, one of which is misfiled under
doc and consists only of "it's dark";
<p>One to commit an untested lightbulb which breaks buildworld,
then back it out five minutes later;
<p>Eight to flame the PR originators for not including patches
in their PRs;
<p>Five to complain about buildworld being broken;
<p>Thirty-one to answer that it works for them, and they must
have cvsupped at a bad time;
<p>One to post a patch for a new lightbulb to -hackers;
<p>One to complain that he had patches for this three years ago,
but when he sent them to -current they were just ignored, and he
has had bad experiences with the PR system; besides, the
proposed new lightbulb is non-reflexive;
<p>Thirty-seven to scream that lightbulbs do not belong in the
base system, that committers have no right to do things like
this without consulting the Community, and WHAT IS -CORE DOING
ABOUT IT!?
<p>Two hundred to complain about the color of the bicycle shed;
<p>Three to point out that the patch breaks style(9);
<p>Seventeen to complain that the proposed new lightbulb is
under GPL;
<p>Five hundred and eighty-six to engage in a flame war about
the comparative advantages of the GPL, the BSD license, the MIT
license, the NPL, and the personal hygiene of unnamed FSF
founders;
<p>Seven to move various portions of the thread to -chat and
-advocacy;
<p>One to commit the suggested lightbulb, even though it shines
dimmer than the old one;
<p>Two to back it out with a furious flame of a commit message,
arguing that FreeBSD is better off in the dark than with a dim
lightbulb;
<p>Forty-six to argue vociferously about the backing out of the
dim lightbulb and demanding a statement from -core;
<p>Eleven to request a smaller lightbulb so it will fit their
Tamagotchi if we ever decide to port FreeBSD to that platform;
<p>Seventy-three to complain about the SNR on -hackers and -chat
and unsubscribe in protest;
<p>Thirteen to post "unsubscribe", "How do I unsubscribe?", or
"Please remove me from the list", followed by the usual footer;
<p>One to commit a working lightbulb while everybody is too busy
flaming everybody else to notice;
<p>Thirty-one to point out that the new lightbulb would shine
0.364% brighter if compiled with TenDRA (although it will have
to be reshaped into a cube), and that FreeBSD should therefore
switch to TenDRA instead of EGCS;
<p>One to complain that the new lightbulb lacks fairings;
<p>Nine (including the PR originators) to ask "what is MFC?";
<p>Fifty-seven to complain about the lights being out two weeks
after the bulb has been changed.
<p><em><url url="mailto:nik@freebsd.org" name="Nik Clayton">
adds:</em>
<p><em/I was laughing quite hard at this./
<p><em/And then I thought, "Hang on, shouldn't there be '1 to
document it.' in that list somewhere?"/
<p><em/And then I was enlightened :-)/
</sect>