On 18 January 2013 13:55, Chet Ramey wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 1/18/13 1:30 AM, Mike Frysinger wrote:
>> this is somewhat a continuation of this thread:
>> http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html
>>
>> i've gotten more or less the same
On 30 January 2013 17:48, Chet Ramey wrote:
>> a simple patch to workaround/fix the issue by Yuta SATOH:
>> --- bash-4.2/redir.c
>> +++ bash-4.2/redir.c
>> @@ -632,7 +632,9 @@
>> }
>>else
>> {
>> - fd = open (filename, flags, mode);
>> + do {
>> + fd = open (filename, f
Forwarding an interesting posting from Roland Mainz who did an
investigation why signal trap processing in ksh93, bash and dash is
currently not reliable.
Lionel
-- Forwarded message --
From: Roland Mainz
Date: 3 June 2013 15:22
Subject: Re: [ast-developers] Realtime signal issue
On 6 June 2013 11:29, Lionel Cons wrote:
> Forwarding an interesting posting from Roland Mainz who did an
> investigation why signal trap processing in ksh93, bash and dash is
> currently not reliable.
>
> Lionel
>
PS: malloc() from AT&T libast, used by ksh93, is async sign
On 2 July 2013 22:44, Eric Blake wrote:
> On 07/02/2013 12:20 PM, Chris Irvine wrote:
>> I tried to download the BASH for my Windows 7 computer with SUA (services
>> for Unix installed). The latest download script, config.guess, was used and
>> the configure command failed with an error. I have
On 15 July 2013 15:35, Chet Ramey wrote:
> On 7/14/13 2:38 PM, Cedric Blancher wrote:
>> The tests below is from the ongoing work of David Korn and Roland
>> Mainz to make signals in ksh93 reliable and predictable (so far no
>> shell tested really does it). I derived one of their tests and found
>
On 15 October 2013 22:44, Joshuah Hurst wrote:
> On Tue, Oct 15, 2013 at 10:36 PM, Chet Ramey wrote:
>> On 10/15/13 4:27 PM, Joshuah Hurst wrote:
>>
> What happened to the patch for cd -@ to handle NFSv4+Windows alternate
> streams? ksh93 already has this feature since quite some time and
On 16 October 2013 14:19, Lionel Cons wrote:
> On 15 October 2013 22:44, Joshuah Hurst wrote:
>> On Tue, Oct 15, 2013 at 10:36 PM, Chet Ramey wrote:
>>> On 10/15/13 4:27 PM, Joshuah Hurst wrote:
>>>
>>>>>> What happened to the patch for cd -@ to
On systems with O_XATTR the bash git devel branch fails due a misnamed
buffer used for cd -@ support:
gcc -c -DHAVE_CONFIG_H -DSHELL -I. -I.. -I.. -I../include -I../lib
-I. -DSOLARIS -DDEBUG -g -O2 cd.c || ( rm -f cd.c ; exit 1 )
./cd.def: In function `cdxattr':
./cd.def:219: error: `buff' un
On 5 November 2013 22:56, Chet Ramey wrote:
>> > I'm interested in the patch if cd -@ file works like in ksh. Or
>> > whatever, just send the patch that I can test it.
>> >
>> > Thank you.
>>
>> Again. Any patch or git pull tarball which we could try?
>
> The cd -@ option is available in the `deve
Chet, below is a simple testcase for cd -@ / O_XATTR support:
./bash -c 'set -o errexit ; touch foo ; runat foo "echo hello1
>myxattr" ; cd -@ foo ; exec {n}<>myxattr ; cd -P .. ; cat <&$n ;
true'
This should print 'hello1'.
Any suggestion where this test can be placed?
Lionel
On 6 November 2013 13:16, Joshuah Hurst wrote:
> Chet, on Solaris the /devices filesystem does not support extended
> attributes (O_XATTR), yet cd -@ returns 0 (success):
>
> ./bash -c 'cd -@ /devices 2>/dev/null; echo $?'
> 0
> ~/bin/ksh -c 'cd -@ /devices 2>/dev/null; echo $?'
> 1
>
> truss show
On 21 January 2014 01:16, Elliott Forney wrote:
> I find it a little unpleasant that cd echoes the new working directory
> when CDPATH is used to locate the new directory (I already have the
> working directory in my prompt). I understand that this is behavior
> is mandated by POSIX but I wonder
Thank you for the cd -@ / O_XATTR support!!
Lionel
On 27 February 2014 14:12, Chet Ramey wrote:
> Introduction
>
>
> The first public release of bash-4.3 is now available with the URLs
>
> ftp://ftp.cwru.edu/pub/bash/bash-4.3.tar.gz
> ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz
>
14 matches
Mail list logo
