Date: Fri, 2 Oct 1998 09:19:22 +0200 (MET DST)
From: Olivier Perron <perron AT art DOT alcatel DOT fr>
X-Sender: perron AT rtbsci146s
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: Olivier Perron <olivier DOT perron AT art DOT alcatel DOT fr>, djgpp AT delorie DOT com
Subject: Re: /dev/null problems with bash when rebuild from sources
In-Reply-To: <Pine.SUN.3.91.981001211736.18395R-100000@is>
Message-Id: <Pine.GSO.4.05.9810020916001.26036-100000@rtbsci146s>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 1 Oct 1998, Eli Zaretskii wrote:

> 
> On Tue, 29 Sep 1998, Olivier Perron wrote:
> 
> > With that version of bash, if I type: echo "foo" >/dev/null
> > I have the following error: bash: /dev/null: No such file or directory
> > (ENOENT)
> 
> This is a bug in stock v2.01 libc.a.  Get the patched libc (see the
> FAQ for a URL), rebuild Bash, and this problem should go away.
> 
> (The bug is in the function `_truename' that is called by `stat': the
> version bundled with stock v2.01 didn't support /dev/foo names.)
> 
Yes, but I do *have* the patched libc with the _truename *you* gave me a
couple of weeks ago when I had to rebuild bash !
So, I'm completly lost !
On which libc should I rely ? on which patches ?

Olivier.