Sorry that I cannot help with your specific error, but I do have some
insight, and a funny story to tell....
In the old days, it was very common for UNIX source code to contain all
sorts of commentary, quips and often the naming of variables used within
the source was quite creative. The variable name "luser", representing a
local user, and making a derrogatory slap at the same time, comes
immediately to mind. Often, an error condition that should never never
occur will have a diagnostic message that is irreverent and funny.
Unfortunately, for those of us who read source, these departures are
becoming less frequent as the code is "sanitized" for public comsumption.
Anyway, about 15 years ago, while developing a 80286 version of AIX under
contract for IBM, we encountered the following scenario....
A level 2 VP, was demonstrating a beta version of the port to some
executives and engineers at IBM when the following message appeared.
"Heat shield failure upon re-entry, shutting down" ....
They removed the cover from the case and even placed fans adjacent to the
box to help cool the unit, but to no avail...
It turns out that one of the kernel programmers had worked also at JPL,
and was coding some intense driver routine where interrupts had to be
disabled. This makes the code "non-reentrant", meaning that it must not
be interrupted. Switching tasks during this period of suspended
interrupts is forbidden, and should never never occur (except in beta :-).
So this programmer inserted his own error message, which should never
never be seen that included a bit of humor. The code was "re-entered" and
the machine halted. The part about the heat shield was a diversion for
the readers of the source. Referring to the heat shield on the re-entry
vehicle under development at Jet Propulsion Labs.
The results were quite unexpected however, and fortunately, the VP had a
sense of humor, and enjoyed telling this story. I think the folks at IBM
also found it funny...
Ergo......
"The intruments are crazy eject eject!" probably means that you have
stumbled upon a condition that should never never occur in the low level
driver. Any other diagnostic would probably be greek to you anyway. Have
a look at the source for that module, you will likely see more funny quips
and quotes.
I once saw a bit of code that contained a flaming diatribe on the poor
programming skills of a fellow programmer (who was explicitly named in the
source) and how crappy his code was and how it was making it impossible
to do this correctly. It was a funny read. I am sure it was removed many
years ago...
On Tue, 27 Aug 2002, Ben Smith wrote:
> I am trying to load Trinux with a 3com fast ethernet
> pcmcia card model 3ccfe575bt-d. As far as I can tell
> this nic is support and the drivers are apart of the
> default package. I get a strange error about something
> being crazy when it tries to detect eth0. The exact
> message is interface eth0 does not exist! The
> instruments are crazy eject eject!
> I am not a linux pro but this error seems like an
> inside joke to me.
>
> Please help
>
> Ben
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Trinux-talk mailing list
> Tri...@li...
> https://lists.sourceforge.net/lists/listinfo/trinux-talk
>
--
--------------------
Timothy Burt
General Manager
Arbor Group LLC
Los Angeles, Calif. USA
|
