File: 7.html

package info (click to toggle)
lg-issue36 2-4
  • links: PTS
  • area: main
  • in suites: woody
  • size: 2,920 kB
  • ctags: 242
  • sloc: makefile: 36; sh: 4
file content (395 lines) | stat: -rw-r--r-- 14,308 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<META NAME="generator" CONTENT="lgazmail v1.1G.e">
<TITLE>The Answer Guy 36: 
An Anthropologist Asks About the Linux "Process"
</TITLE>
</HEAD><BODY BGCOLOR="#FFFFFF" TEXT="#000000"
	LINK="#3366FF" VLINK="#A000A0">
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<H4>"The Linux Gazette...<I>making Linux just a little more fun!</I>"</H4>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<center>
<H1><A NAME="answer">
	<img src="../../gx/dennis/qbubble.gif" alt="(?)" border="0" align="middle">
	<font color="#B03060">The Answer Guy</font>
	<img src="../../gx/dennis/bbubble.gif" alt="(!)" border="0" align="middle">
</A></H1> 
<BR>
<H4>By James T. Dennis,
	<a href="mailto:answerguy@ssc.com">answerguy@ssc.com</a><BR>
	Starshine Technical Services,
	<A HREF="http://www.starshine.org/">http://www.starshine.org/</A> 
</H4>
</center>

<p><hr><p>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<!-- begin 7 -->
<H3 align="left"><img src="../../gx/dennis/qbubble.gif" height="50" width="60"
	  alt="(?) " border="0">
An Anthropologist Asks About the Linux "Process"
</H3>


<p><strong>From donald.braman on Mon, 23 Nov 1998  
</strong></p>
<!-- ::
An Anthropologist Asks About the Linux "Process"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:: -->
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
I don't know if you cover non-technical questions, but here goes...
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
Then you haven't read enough of the back issues.
</BLOCKQUOTE>
<BLOCKQUOTE>
I babble about all sorts of things and have even been
know to respond to questions that have NOTHING to do
with Linux.  (Usually those responses are less than
cordial --- but hey, you can have answers that are
good, courteous, quick, and/or free (pick any three)).
</BLOCKQUOTE>
<BLOCKQUOTE>

</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
I'm interested in finding a summary of the process by which LINUX
is maintained and updated.
</STRONG></P>
<P><STRONG>
Where is Linus in the LINUX community and loose organizational
structure, and how does he decide what to do with all of the stuff
he get? (I always see "Linus just released kernel 2.xxx"
messages.)
</STRONG></P>
<P><STRONG>

</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
Linus "owns" the kernel.  He primarily focuses his
work on the developmental kernels (2.1.x right now ---
will probably be 2.3.x within a month or so).  The
stable kernels (2.0 currently) are largely maintained by
Alan Cox, though they are still sent to Linus for final
approval and official release.
</BLOCKQUOTE>
<BLOCKQUOTE>
When Linus decides that the work is complete on the
2.1 series he'll declare it to be "2.2" --- then
he'll start a 2.3 series (and there will be a quick
flood of patches posted to that, since we've been in
"feature freeze" for a couple of months and there are
people who have been privately working on some
new features in anticipation of the next development
cycle.
</BLOCKQUOTE>
<BLOCKQUOTE>
I've heard that Linus plans to turn the maintenance of
2.2 immediately over to Alan and Stephen Tweedie.  That
will allow him to focus on the next version exclusively.
</BLOCKQUOTE>
<BLOCKQUOTE>
Although there has been some effort to minimize the number
of bugs that will be in the 2.2 release --- it is almost
certain that we'll have at least a few 2.2.x releases within
the first few months.  Many of these will account for bugs
that only affect a small subset of the available hardware
configurations (one user in 10,000 or less).  For the 1.0
series we had about nine releases to the stable kernel set.
For the 1.2 series we had about 13 or so.  In 2.0 we have
had 36 (the versioning skipped from 1.3 to 2.x due major
structural changes in the kernel).  Don't just graph that
to project an estimate --- unless you also scale the graph
over the time frames involved.  Even than you'd find some
anomalies --- the differences between 1.2 and 2.0 are as
great as the versions numbers suggest.
</BLOCKQUOTE>
<BLOCKQUOTE>
As for how Linus decides what to incorporate and what to
ignore or kick back ... that's one of the mysteries to
which mere acolytes and initiates such as myself are not
privvy.
</BLOCKQUOTE>
<BLOCKQUOTE>
Linus is swamped.  He gets direct e-mailed patches from
countless programmers and programming students around the
world.  (The Savvy ones actually read the FAQ at
<A HREF="http://www.tux.org/lkml">http://www.tux.org/lkml</A> 
before trying to contribute to the Linux kernel).
</BLOCKQUOTE>
<BLOCKQUOTE>
See below for more on that.
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
What if, no offense intended, Linus died tomorrow?
</STRONG></P>
<P><STRONG>

</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
This class of events has been discussed (usually in less
morbid terms --- using the term "retiring" rather than
references to "expiriing").
</BLOCKQUOTE>
<BLOCKQUOTE>
This would be a great loss to the Linux community.
</BLOCKQUOTE>
<BLOCKQUOTE>
However, the sources are out there under a license that
ensure that they will remain freely available and "alive"
(able and likely to be upgraded, ported to new platforms,
and generally improved upon).
</BLOCKQUOTE>
<BLOCKQUOTE>
The great advantage that Linux has had over 
<A HREF="http://www.freebsd.org/">FreeBSD</A>, (and
it's brethren) has been Linus.  He focuses on the kernel,
and on code and quality, and almost completely eschews
politics.  He let's others deal with "user space" issues
(libraries, compilers, and all of the suites of utilities
and applications that go into any Linux distribution).
</BLOCKQUOTE>
<BLOCKQUOTE>
We've benefitted immensely from our "benign dictactor" model
--- we accepted Linus as "the Linux kernel God" (we hold
none before him and we're monotheistic in this regard).
</BLOCKQUOTE>
<BLOCKQUOTE>
When Linus eventually retires, moves on to other conquests,
or whatever (may it happen long after my own demise), then
the hope among the Linux kernel developers is that we'll be
able to adopt, appoint, agree upon a successor --- a new
benign dictator.  That might be someone like Alan Cox, or
Stephen Tweedie, or it might be just about anyone who's
name appears regularly enough on the Linux-kernel mailing
list  (I don't know enough to say).
</BLOCKQUOTE>
<BLOCKQUOTE>
Linus as jokingly referred to his daughters and Linus 2.0
and 3.0 (we could make it a heriditary oligarchy, if
they take the interest and aquire the proficiency).  Check
back in with us in about 15 years on that.
</BLOCKQUOTE>
<BLOCKQUOTE>

</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
Further, I'd like to find a place where (tentative) plans for
future releases are discussed, and even a vague timeline is
given. In short, is there a project management site/organization
that contains a summary of (debates about) where LINUX is going
and how it's going to get there?
</STRONG></P>
<P><STRONG>

</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
Here's the real fun question.  Anyone who's seriously
involved in Linux kernel development is subscribed to the
Linux-kernel mailing list hosted by Rutgers University (Read
the FAQ listed above for exact instructions on how to
subscribe, where to find archives and how to search through
them).
</BLOCKQUOTE>
<BLOCKQUOTE>
linux-kernel is a very busy mailing list.  I've received
well over nine thousand pieces of e-mail on that list in
just the last few months.  It gets close to a hundred items
per day.  (The only Internet mailing list that I've been on
that seemed busier was the old cypherpunks list when it was
hosted at Toad Hall --- and maybe the Firewalls list that
was started by Brent Chapman at Great Circle Associates).
</BLOCKQUOTE>
<BLOCKQUOTE>
With that volume of traffic, you can be sure that many busy
developers (such as Linus) don't get to read everything.
(Linus has a family life and a full-time job --- mostly in
addition to his kernel work; although Transmeta apparently
does provide him with some work time to devote to Linux ---
as per his contract with them).
</BLOCKQUOTE>
<BLOCKQUOTE>
Of course, the best way for you to learn about the
social dynamics of the Linux kernel developers is to
immerse yourself in it for awhile.  Start with some
research (read the FAQ, and a month or two's worth of
the archives), then subscribe to the list and lurk
(read and don't post) for a month.
</BLOCKQUOTE>
<BLOCKQUOTE>
If you're doing research on us --- please let us know
where we can read any papers that you put together.  We
have one participant (esr, or Eric S. Raymond who has
referred to himself as the Linux community's
"anthropologist" but it might be interested to have an
alternative set of opinions from a more "objective" source).
</BLOCKQUOTE>
<BLOCKQUOTE>
(Eric has been a hacker since before Linux was developed.
He helped to compile and publish the &quot;New Hacker's
Dictionary&quot; --- which is also a pretty good source of
background if you want to understand the Linux community
as a subculture.  Take it with a grain of salt, of course
--- but read it anyway).
</BLOCKQUOTE>
<BLOCKQUOTE>

</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
Donald Braman
<br>Yale Anthropology
</STRONG></P>

<!-- sig -->

<!-- end 7 -->
<!--startcut ======================================================= -->
<P> <hr> <P>
<H5 align="center"><a href="http://www.linuxgazette.com/ssc.copying.html"
        >Copyright &copy;</a> 1999, James T. Dennis
<BR>Published in <I>The Linux Gazette</I> Issue 36 January 1999</H5>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<P align="center">
<table width="98%"><tr valign="center" align="center">
<td rowspan="3" colspan="6"><A HREF="../lg_answer36.html"><IMG
        SRC="../../gx/dennis/answernew.gif"
        ALT="[ Answer Guy Index ]"></A></td>
  <TD><A HREF="./a.html">a</A></TD>
  <TD><A HREF="./b.html">b</A></TD>
  <TD><A HREF="./c.html">c</A></TD>
  <TD><A HREF="./1.html">1</A></TD>
  <TD><A HREF="./2.html">2</A></TD>

  <TD><A HREF="./3.html">3</A></TD>
  <TD><A HREF="./4.html">4</A></TD>
  <TD><A HREF="./5.html">5</A></TD>
  <TD><A HREF="./6.html">6</A></TD>
  <TD><A HREF="./7.html">7</A></TD>

  <TD><A HREF="./9.html">9</A></TD>
  <TD><A HREF="./10.html">10</A></TD>
  <TD><A HREF="./11.html">11</A></TD>
  <TD><A HREF="./12.html">12</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./15.html">15</A></TD>
  <TD><A HREF="./16.html">16</A></TD>
  <TD><A HREF="./18.html">18</A></TD>
  <TD><A HREF="./19.html">19</A></TD>

  <TD><A HREF="./20.html">20</A></TD>
  <TD><A HREF="./21.html">21</A></TD>
  <TD><A HREF="./22.html">22</A></TD>
  <TD><A HREF="./23.html">23</A></TD>
  <TD><A HREF="./24.html">24</A></TD>

  <TD><A HREF="./25.html">25</A></TD>
  <TD><A HREF="./26.html">26</A></TD>
  <TD><A HREF="./27.html">27</A></TD>
  <TD><A HREF="./28.html">28</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./29.html">29</A></TD>
  <TD><A HREF="./31.html">31</A></TD>
  <TD><A HREF="./32.html">32</A></TD>
  <TD><A HREF="./33.html">33</A></TD>
  <TD><A HREF="./34.html">34</A></TD>

  <TD><A HREF="./35.html">35</A></TD>
  <TD><A HREF="./36.html">36</A></TD>
  <TD><A HREF="./37.html">37</A></TD>
  <TD><A HREF="./38.html">38</A></TD>
  <TD><A HREF="./39.html">39</A></TD>

  <TD><A HREF="./40.html">40</A></TD>
  <TD><A HREF="./41.html">41</A></TD>
  <TD><A HREF="./42.html">42</A></TD>
  <TD><A HREF="./44.html">44</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./45.html">45</A></TD>
  <TD><A HREF="./46.html">46</A></TD>
  <TD><A HREF="./47.html">47</A></TD>
  <TD><A HREF="./48.html">48</A></TD>
  <TD><A HREF="./49.html">49</A></TD>
  <TD><A HREF="./50.html">50</A></TD>

  <TD><A HREF="./51.html">51</A></TD>
  <TD><A HREF="./52.html">52</A></TD>
  <TD><A HREF="./53.html">53</A></TD>
  <TD><A HREF="./54.html">54</A></TD>
  <TD><A HREF="./55.html">55</A></TD>

  <TD><A HREF="./56.html">56</A></TD>
  <TD><A HREF="./57.html">57</A></TD>
  <TD><A HREF="./60.html">60</A></TD>
  <TD><A HREF="./61.html">61</A></TD>
  <TD><A HREF="./62.html">62</A></TD>

  <TD><A HREF="./63.html">63</A></TD>
  <TD><A HREF="./64.html">64</A></TD>
  <TD><A HREF="./65.html">65</A></TD>
  <TD><A HREF="./66.html">66</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./67.html">67</A></TD>
  <TD><A HREF="./69.html">69</A></TD>
  <TD><A HREF="./72.html">72</A></TD>
  <TD><A HREF="./76.html">76</A></TD>
  <TD><A HREF="./77.html">77</A></TD>
  <TD><A HREF="./78.html">78</A></TD>

  <TD><A HREF="./79.html">79</A></TD>
  <TD><A HREF="./80.html">80</A></TD>
  <TD><A HREF="./81.html">81</A></TD>
  <TD><A HREF="./82.html">82</A></TD>
  <TD><A HREF="./84.html">84</A></TD>

  <TD><A HREF="./85.html">85</A></TD>
  <TD><A HREF="./86.html">86</A></TD>
  <TD><A HREF="./87.html">87</A></TD>
  <TD><A HREF="./91.html">91</A></TD>
  <TD><A HREF="./94.html">94</A></TD>

  <TD><A HREF="./95.html">95</A></TD>
  <TD><A HREF="./96.html">96</A></TD>
  <TD><A HREF="./97.html">97</A></TD>
  <TD><A HREF="./98.html">98</A></TD>
</tr></table>
	</P>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<A HREF="../lg_toc36.html"
        ><IMG SRC="../../gx/indexnew.gif" ALT="[ Table Of Contents ]"></A>
<A HREF="../../index.html"
        ><IMG SRC="../../gx/homenew.gif" ALT="[ Front Page ]"></A>
<A HREF="../lg_bytes36.html"
        ><IMG SRC="../../gx/back2.gif" ALT="[ Previous Section ]"></A>
<A HREF="../larriera.html"
        ><IMG SRC="../../gx/fwd.gif" ALT="[ Next Section ]"></A>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
</BODY></HTML>
<!--endcut ========================================================= -->