Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site cbosgd.UUCP
Path: utzoo!watmath!clyde!cbosgd!mark
From: mark@cbosgd.UUCP (Mark Horton)
Newsgroups: net.micro.att,net.unix
Subject: Re: Problems with the 7300
Message-ID: <1160@cbosgd.UUCP>
Date: Thu, 9-May-85 14:49:25 EDT
Article-I.D.: cbosgd.1160
Posted: Thu May  9 14:49:25 1985
Date-Received: Fri, 10-May-85 03:19:16 EDT
References: <166@timeinc.UUCP>
Organization: AT&T Bell Laboratories, Columbus, Oh
Lines: 20
Xref: watmath net.micro.att:12 net.unix:4465

In article <166@timeinc.UUCP> greenber@timeinc.UUCP (Ross Greenberg) writes:
>Escaping to shell (or forking to vi) from
>$ ls -lR / | more   (or ls -lR / | page)
>barfs out.  Funny error messages, some endless loops, etc.
>Looks like a piping problem.

Why would you want to vi the output of the ls command?  This is an old
bug in more that was fixed by 4.2BSD - it's execing vi with stdin set
to the pipe, so the output of ls is being taken by vi as keyboard commands.
More now beeps if you try to do something this silly.  I'm not sure what
pg does in SVR2.

>AT&T claim 9 users.  Could be.  I felt it was *VERY*
>slow with one user.

More specifically, the disk is slow, compared to the speed of everything
else.  CPU processes seem quite fast.  However, in a disk that small and
that inexpensive, you can't expect a lot of speed.

	Mark