From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wren.cs.unc.edu ([152.2.128.86]) by hawkwind.utcs.toronto.edu with SMTP id <25883>; Tue, 9 May 2000 18:53:15 -0400 Received: from rukbat.cs.unc.edu (rukbat.cs.unc.edu [152.2.133.170]) by wren.cs.unc.edu (8.9.3/8.9.3) with ESMTP id TAA14087 for ; Mon, 8 May 2000 19:25:26 -0400 (EDT) Received: (from tell@localhost) by rukbat.cs.unc.edu (8.9.3/8.9.3) id TAA29982; Mon, 8 May 2000 19:25:25 -0400 (EDT) Date: Mon, 8 May 2000 19:25:25 -0400 From: Stephen Tell To: rc@hawkwind.utcs.toronto.edu Subject: Re: building rc on QNX4 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 8 May 2000, Tim Goodwin wrote: > Date: Mon, 8 May 2000 05:15:01 -0400 > From: Tim Goodwin > To: rc@hawkwind.utcs.toronto.edu > Subject: Re: building rc on QNX4 > > > In order to make this work, you need to find a utility that is > > guaranteed to read no more than the first line of standard input. > > Yup. What if such a utility were distributed with rc, or as part of an > rc-utils package? I suppose that would be sufficient. The workaround I've used has been this: var = `{sh -c 'read t; echo $t'} # read var Starting up sh just to avoid the little bit of code that a read builtin would add to rc itself or an included utility seems a bit rediculous. -- Steve Tell | tell@cs.unc.edu | http://www.cs.unc.edu/~tell | KF4ZPF On Leave from UNC working at Chip2Chip, Inc. tell@chip2chip.com/919-929-0991