Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!sundc!gouldsd!mjranum
From: mjranum@gouldsd.UUCP
Newsgroups: comp.os.minix,rec.ham-radio,comp.windows.x,comp.sys.atari.st
Subject: Re: MINIX - STD EXTENSIONS
Message-ID: <475@gouldsd.UUCP>
Date: Tue, 3-Mar-87 08:39:43 EST
Article-I.D.: gouldsd.475
Posted: Tue Mar  3 08:39:43 1987
Date-Received: Thu, 5-Mar-87 20:01:36 EST
References: <336daeb9.9540@apollo.uucp>
Organization: Gould Electronics, Landover MD.
Lines: 41
Keywords: MINIX PACKET TCP IP X WINDOWS
Xref: utgpu comp.os.minix:379 rec.ham-radio:667 comp.windows.x:185 comp.sys.atari.st:1822
Summary: oh, sure....

In article <336daeb9.9540@apollo.uucp>, hays@apollo.uucp (John Hays) writes:
> would like to suggest the following two items be considered for 
> STANDARD EXTENSIONS:
> 
>         1. MIT's X Window System - for those with bitmaped screens
> 
>         2. KA9Q's TCP/IP (Phil Karn) implementation.  This code,
[blah,blah,blah...]

Let's be real, here, guys. From what I understand (not having had a chance to
get my minix up, running, and beaten on) there are even questions as to whether
the hard disk drivers function properly. You are talking about implementing
an awful lot of fancy stuff on some pretty brain-damaged hardware.

I am sick of seeing all this 'when I get suntools running on minix I'll post to
the net" shit. Don't waste the net's time telling us about the great things
you're going to do unless you have a beta-test version :-) 

I think it might be more productive to worry (in order) about exhaustively
testing minix, and making more portable drivers for a variety of hard disk
controllers, and then maybe clearing up the odd bug here and there. TCP/IP
is really very nice, but who wants to talk to a PC anyway ? I'd never let 
one on my network unless the sucker had a better security system than being
able to boot off of *ANY* floppy you choose (hence any /etc/passwd, etc). 

Please wake up and smell the roses, guys. UNIX wasn't written overnight, and
it certainly wasn't written by 800 usenet messages saying "well, I'd really
like to see this implemented..." or "I plan to port all the code for KERMIT
and build it into the kernel as a local area network", blah, blah, blah...

I suggest we maybe form a talk.minix.wild.wetdream, or a comp.os.fantasy
for you guys, and the rest of us can concentrate on simpler things like
maybe making it a bit more portable, robust, and adding some of our favorite
AT&T-like tools. Ferget the TCP/IP - the basics like 'sed' and 'lex' are
a lot more likely to be missed.

--mjr();

-- 
"It is better to shred the bugger than to bugger the shredder."
					-ancient doltic proverb.