*BSD News Article 24915


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sgiblab!swrinde!cs.utexas.edu!bga.com!bga.com!nobody
From: boyd@bga.com (Boyd Faulkner)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: gcc/ksh bugs
Date: 10 Dec 1993 14:52:14 -0600
Organization: Real/Time Communications - Bob Gustwick and Associates
Lines: 43
Message-ID: <2eanhu$1li@ghostwheel.bga.com>
References: <10@w2xo.pgh.pa.us> <2e7nt8$c4m@pdq.coe.montana.edu>
NNTP-Posting-Host: ghostwheel.bga.com
Keywords: gcc ksh bugs

In article <2e7nt8$c4m@pdq.coe.montana.edu>,
Nate Williams <nate@bsd.coe.montana.edu> wrote:
>In article <10@w2xo.pgh.pa.us>, Jim Durham <durham@w2xo.pgh.pa.us> wrote:
>>Hello,
>>
>
>>The ksh binary from freebsd.cdrom.com works fine, except that
>>if you pipe the output of a command like "sed" to a file, it writes
>>a bizillion nulls to the front of the file.
>
>No idea.
>

I find that ls > bozo produces the file bozo with the same
results.  Redirection doesn't work.  Apparently the file pointer
doesn't point where you think it does.  I was working on the problem
until I got shipped to Oregon for the rest of the year.  I hope
to look at it again when I get home.  Anyone else is welcome
to fix it I'm sure.  (No I don't maintain it.)  

As best I remember the code uses lseek( , 1) to reset from the 
current position and the current position should be correct.
I guess it gets corrupted.

I can tell you that ksh -c ls > bozo does work correctly.

mail jim < bozo where bozo is not empty produces an empty mail message.

Good Luck.
ksh on BSDI doesn't have this problem.

Boyd
>
>
>Nate
>
>-- 
>nate@bsd.coe.montana.edu     |  Freely available *nix clones benefit everyone,
>nate@cs.montana.edu          |  so let's not compete with each other, let's
>work #: (406) 994-4836       |  compete with folks who try to tie us down to
>home #: (406) 586-0579       |  proprietary O.S.'s (Microsloth) - Me