A guy I know sent me http://www.ssc.com/linews/debspace.html in a message titled something like "Linux running on Space Shuttle". Which scared me for a second -- I was afraid they were using Linux to control the space shuttle. (Mind you, I like Linux, and run it on my system at home. I'm just not sure it's ready for Space Shuttle avionics.) Which got me thinking. Linux on an imbedded system. Hmm. What's next, Tomahawks? Imagine: cg-67 > telnet bang27 Trying... Connected to bang27.cg-67.navy.mil Debian Linux (root@thawk.tucson.hughesmissiles.com) (ttyp1) login: weps Password: Last login: Mon Mar 10 09:39:43 from depot77.navsup.navy.mil ****************************************************************** Welcome to Bang 27 - TLAM-D Tue Apr 1 08:58:40 EST 1997 bang27> emacs & [1] 264 bang27> [1] Done emacs bang27> make config Make: Don't know how to make config. Stop. bang27> cd targets bang27> make config Make: Don't know how to make config. Stop. bang27> make [ config.h : config.status ] ./config.status creating Makefile creating config.h creating targets.h config.h is unchanged targets.h is changed gcc -o targ targ.c gcc guid.o nav.o gps.o dsmac.o targ.o toa.o -o flyme bang27> flyme -d flyme: platform... aligned flyme: interlock... engaged flyme: VLS door... open flyme: Booster... ^C^A^K^DÀ@ Connection reset by peer cg-67> mail co@cg-67.navy.mil Sorry, Captain. I just ran flyme with the -d option, but for some reason the missile launched anyway. I guess the guys at Hughes must have compiled with -d disabled again. Could you ask Commo to call their Tucson plant and tell them they either need to set up the remote link and disable the bird or evacuate their building? Also, somebody need to tell them that using "blowme" as a default password could get us in the same kind of trouble as the Tailhook types. Weps.
(From the "Rest" of RHF)