Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucsd!ames!oliveb!pyramid!ctnews!UNIX386!mark
From: mark@UNIX386.Convergent.COM (Mark Nudelman)
Newsgroups: comp.arch
Subject: Re: 80386 vs. 68030
Message-ID: <213@UNIX386.Convergent.COM>
Date: 16 Dec 88 23:09:51 GMT
References: <3283@mipos3.intel.com> <6360@killer.DALLAS.TX.US>
Organization: Convergent Technologies, San Jose, CA
Lines: 33

In article <6360@killer.DALLAS.TX.US>, elg@killer.DALLAS.TX.US (Eric Green) writes:
> Sys V sux. I'm typing this from a 3b2 running Sys V.3 (the
> latest/greatest), and while it may have some nice underpinnings
> (streams and everything), it's currently missing some of the
> best-loved pieces of BSD4.x -- e.g. I can't type "what" or "finger" or
> "talk" or "uptime" or .... 

That's funny... I'm running SVR3 and I can type "what" or "finger"
or "talk" or "uptime". 

It says "what: not found",  "finger: not found", ....

:-)

> not to mention that it totally lacks job
> control signals, so that if I run something like, say, "shl" to get
> the same functionality, my editors don't know they've been
> suspended/resumed and thus can't redraw the screen automagically for
> me. Not to mention that half of Sys V doesn't understand the
> pseudo-ttys that "shl" uses, e.g. good old "write", primitive as it
> is, barfs and aborts when I try to run it under "shl".

I think job control is one of the most important features SysV is
missing.  At least it will be in SVR4.

Too bad the rest of the BSD crud will be as well.  :-(


Mark Nudelman
{sun,decwrl,ihnp4!hplabs}!pyramid!ctnews!UNIX386!mark


	I never said it.