version 1, including all changes.
.
| Rev |
Author |
# |
Line |
| 1 |
StuartYeates |
1 |
!!!Geekerata |
| |
|
2 |
|
| |
|
3 |
(A UNIX Analog of Desiderata (Max Ehrman, 1927))%%% |
| |
|
4 |
(mainly as addressed to a network process) |
| |
|
5 |
|
| |
|
6 |
Badri Krishnamoorthy%%% |
| |
|
7 |
badri@srtc.com |
| |
|
8 |
|
| |
|
9 |
|
| |
|
10 |
Route placidly amid channel noise and network failures,%%% |
| |
|
11 |
And remember what throughput there may be in executing all alone. |
| |
|
12 |
|
| |
|
13 |
As far as possible, without overflowing buffer%%% |
| |
|
14 |
Be on communicative terms with all processes.%%% |
| |
|
15 |
Broadcast your data quietly and clearly%%% |
| |
|
16 |
And listen(2) to others.%%% |
| |
|
17 |
Even to the null and the unreachable,%%% |
| |
|
18 |
They too have their requests.%%% |
| |
|
19 |
Avoid long and argumentative sessions%%% |
| |
|
20 |
They are burdensome to the ether. |
| |
|
21 |
|
| |
|
22 |
If you compare your priority with others'%%% |
| |
|
23 |
You may become vain or bitter%%% |
| |
|
24 |
For always there will be greater and lesser processes than yourself.%%% |
| |
|
25 |
|
| |
|
26 |
Enjoy your CPUtime as well as your idletime.%%% |
| |
|
27 |
Keep cognizance of your portmapper, however low-level%%% |
| |
|
28 |
It is a constant port in the changing mappings of the network.%%% |
| |
|
29 |
|
| |
|
30 |
Exercise caution in your execution,%%% |
| |
|
31 |
For the kernel is full of traps.%%% |
| |
|
32 |
But let this not blind you to what swap space there is;%%% |
| |
|
33 |
Many channels strive for high bandwidths, and everywhere%%% |
| |
|
34 |
Computing is full of parallelism. |
| |
|
35 |
|
| |
|
36 |
Be yourself. (Check with getpid(2) frequently)%%% |
| |
|
37 |
Especially do not forge NFS file handles.%%% |
| |
|
38 |
Neither be cynical about sockets,%%% |
| |
|
39 |
For in the face of all congestion and delays%%% |
| |
|
40 |
They are as powerful as STREAMS. |
| |
|
41 |
|
| |
|
42 |
|
| |
|
43 |
Take kindly the influx of new requests,%%% |
| |
|
44 |
Gracefully re-prioritizing the older ones. |
| |
|
45 |
|
| |
|
46 |
Nurture support of check-points to rollback from sudden crashes %%% |
| |
|
47 |
But do not thrash pages due to imagined pagefaults:%%% |
| |
|
48 |
Many core dumps are born of bus error or segmentation faults. |
| |
|
49 |
|
| |
|
50 |
Beyond a nominal consideration,%%% |
| |
|
51 |
Be nice(1) to other processes. |
| |
|
52 |
|
| |
|
53 |
You are a child in the kernel space%%% |
| |
|
54 |
No less than the daemons and the device drivers,%%% |
| |
|
55 |
You have a right to execute here.%%% |
| |
|
56 |
And whether or not it is apparent to you%%% |
| |
|
57 |
No doubt the kernel is crashing, though it shouldn't. |
| |
|
58 |
|
| |
|
59 |
Therefore be at peace with your programmer%%% |
| |
|
60 |
However geeky you think s/he is. %%% |
| |
|
61 |
And wherever your read(2)'s and recvfrom(2)'s,%%% |
| |
|
62 |
In the noisy communication channels of the network,%%% |
| |
|
63 |
Keep a valid (void *) buf available in your address space.%%% |
| |
|
64 |
With all its stopped jobs, missing arguments and broken pipes,%%% |
| |
|
65 |
It is still a UNIX shell. |
| |
|
66 |
|
| |
|
67 |
Be backward-compatible.%%% |
| |
|
68 |
Strive to be up and running always. |
