Freebsd Fortunes 4: 1137 of 2327 |
If you don't drink it, someone else will.
|
|
|
Freebsd Fortunes 4: 1138 of 2327 |
If you don't go to other men's funerals they won't go to yours.
-- Clarence Day
|
|
|
Freebsd Fortunes 4: 1139 of 2327 |
If you don't have the time right now,
will you have redo right time later?
|
|
|
Freebsd Fortunes 4: 1140 of 2327 |
If you don't have time to do it right, where
are you going to find the time to do it over?
|
|
|
Freebsd Fortunes 4: 1141 of 2327 |
If you don't know what game you're playing, don't ask what the score is.
|
|
|
Freebsd Fortunes 4: 1142 of 2327 |
If you don't like the way I drive, stay off the sidewalk!
|
|
|
Freebsd Fortunes 4: 1143 of 2327 |
If you don't say anything, you won't be called on to repeat it.
-- Calvin Coolidge
|
|
|
Freebsd Fortunes 4: 1144 of 2327 |
If you don't strike oil in twenty minutes, stop boring.
-- Andrew Carnegie, on public speaking
|
|
|
Freebsd Fortunes 4: 1145 of 2327 |
If you drink, don't park. Accidents make people.
|
|
|
Freebsd Fortunes 4: 1146 of 2327 |
If you ever want to have a lot of fun, I recommend that you go off and program
an imbedded system. The salient characteristic of an imbedded system is that
it cannot be allowed to get into a state from which only direct intervention
will suffice to remove it. An imbedded system can't permanently trust anything
it hears from the outside world. It must sniff around, adapt, consider, sniff
around, and adapt again. I'm not talking about ordinary modular programming
carefulness here. No. Programming an imbedded system calls for undiluted
raging maniacal paranoia. For example, our ethernet front ends need to know
what network number they are on so that they can address and route PUPs
properly. How do you find out what your network number is? Easy, you ask a
gateway. Gateways are required by definition to know their correct network
numbers. Once you've got your network number, you start using it and before
you can blink you've got it wired into fifteen different sockets spread all
over creation. Now what happens when the panic-stricken operator realizes he
was running the wrong version of the gateway which was giving out the wrong
network number? Never supposed to happen. Tough. Supposing that your
software discovers that the gateway is now giving out a different network
number than before, what's it supposed to do about it? This is not discussed
in the protocol document. Never supposed to happen. Tough. I think you
get my drift.
|
|