On Fri, 26 Sep 2014 10:25:32 -0400, Chet Ramey wrote:
> On 9/26/14, 10:15 AM, Allodoxaphobia wrote:
>
>> There was another bash upgrade in the FreeBSD ports this A.M.
>> Thinking it might resolve my bash --version problem, I applied it.
>>
>> sigh...
>>
>> | [userid~]bash
>> | /usr/local/bin/ba
On 9/26/14, 10:15 AM, Allodoxaphobia wrote:
> There was another bash upgrade in the FreeBSD ports this A.M.
> Thinking it might resolve my bash --version problem, I applied it.
>
> sigh...
>
> | [userid~]bash
> | /usr/local/bin/bash: warning: x: ignoring function definition attempt
> | /usr/l
On 26 Sep 2014 03:13:57 GMT, Allodoxaphobia wrote:
> On Thu, 25 Sep 2014 23:04:46 -0400, Chet Ramey wrote:
>> On 9/25/14, 9:41 PM, Allodoxaphobia wrote:
>>> Earlier today I performed the `bash` security upgrade on my
>>> | [userid~]uname -rs
>>> | FreeBSD 10.0-RELEASE-p9
>>> machine. I thought t
On Thu, 25 Sep 2014 23:04:46 -0400, Chet Ramey wrote:
> On 9/25/14, 9:41 PM, Allodoxaphobia wrote:
>> Earlier today I performed the `bash` security upgrade on my
>> | [userid~]uname -rs
>> | FreeBSD 10.0-RELEASE-p9
>> machine. I thought to check the version level of `bash` to
>> see what I now h
On 9/25/14, 9:41 PM, Allodoxaphobia wrote:
> Earlier today I performed the `bash` security upgrade on my
> | [userid~]uname -rs
> | FreeBSD 10.0-RELEASE-p9
> machine. I thought to check the version level of `bash` to
> see what I now have:
I can't reproduce this. My patched version of bash giv
