home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.wizards
- Path: sparky!uunet!gumby!wupost!emory!nastar!phardie
- From: phardie@nastar.uucp (Pete Hardie)
- Subject: Re: The Problem with UNIX
- Message-ID: <1992Nov17.205836.10584@nastar.uucp>
- Organization: Digital Transmission Systems, Duluth, GA.
- References: <Bxq6uz.BB8@chinet.chi.il.us> <97716@netnews.upenn.edu> <Bxtx2o.Bo7@fig.citib.com>
- Date: Tue, 17 Nov 1992 20:58:36 GMT
- Lines: 24
-
- In article <Bxtx2o.Bo7@fig.citib.com> gjb@fig.citib.com (Greg Brail) writes:
- >Not too many years ago a bunch of Navy crewmen who hadn't read all the FMs
- >on the USS Vincennes blew up an airliner, killing hundreds of innocent people.
-
- Wasn't that airliner also using a transponder scavenged from a military jet,
- giving it a military 'profile' on radar?
-
- >UNIX is becoming more and more common in commercial environments, but this
- >attitude will drive people away. Fortunately, it's possible to give "Joe
- >User" a reasonable interface and save the command line for the hackers.
-
- Sometimes a command line *is* the reasonable interface.
-
- >That's why I have a Macintosh at home.
-
- Try this: list all the C code files in a given directory on your Mac, using
- the iconinc interface. Only files with '.c' suffix.
-
-
- --
- Pete Hardie: phardie@nastar (voice) (404) 497-0101
- Digital Transmission Systems, Inc., Duluth GA
- Member, DTS Dart Team | cat * | egrep -v "signature virus|infection"
- Position: Goalie |
-