On 9/2/15 11:48 AM, Greg Wooledge wrote:
> On Wed, Sep 02, 2015 at 11:24:42AM -0400, Chet Ramey wrote:
>> On 9/2/15 11:19 AM, Greg Wooledge wrote:
>>> On Wed, Sep 02, 2015 at 10:16:14AM -0500, Dennis Williamson wrote:
The $ is implied.
>>>
>>> That is completely absurd. (And wrong.)
>>
>> Not
On 9/2/15 5:10 PM, Helmut Karlowski wrote:
>> `\c' honor backslash escaping. Since the character becomes \c\\, the
>> subsequent `c' and `]' are literals.
>
> I assume this is only true for "to-be-escaped" characters, that is
>
> $ ` " \
>
> like for ".."-strings? Of course only \ is
2015-09-01 16:23:08 -0400, Greg Wooledge:
> On Tue, Sep 01, 2015 at 03:13:57PM -0500, Dennis Williamson wrote:
> > The version of dash I have handy (0.5.7) has math support which IMHO is
> > broken:
> >
> > $ foo=bar
> > $ bar=5
> > $ echo $foo
> > bar
> > $ echo $((foo))
> > dash: 4: Illegal numb
On 9/2/15 4:48 PM, Chet Ramey wrote:
> On 9/2/15 2:14 PM, Clint Hepner wrote:
>
>> Bash Version: 4.3
>> Patch Level: 30
>> Release Status: release
>>
>> Description:
>>Unexpected word splitting in here string. According to the man page,
>> "Pathname expansion and word splitting are not pe
On Thu, Sep 3, 2015 at 8:45 AM, Stephane Chazelas <
stephane.chaze...@gmail.com> wrote:
> 2015-09-01 16:23:08 -0400, Greg Wooledge:
> > On Tue, Sep 01, 2015 at 03:13:57PM -0500, Dennis Williamson wrote:
> > > The version of dash I have handy (0.5.7) has math support which IMHO is
> > > broken:
> >
On 9/2/15 11:46 PM, ziyunfei wrote:
> Sorry, I didn't understand your reply. What I'm saying is this: \? is shown
> in printf section:
>
> "Causes printf to expand backslash escape sequences in the corresponding
> argument, except that ‘\c’ terminates output, backslashes in ‘\'’, ‘\"’,
> and ‘\?’
On 9/3/15 2:43 AM, Ondrej Oprala wrote:
> We have recently had a customer request for this, and Steve Grubb corrected
> the original patch for auditing. IIRC, aureport-2.4.2 should be able to
> handle the USER_TTY
> events now. With his permission, I'm attaching the new patch.
Thanks for the upda
On Sep 4, 2015, at 3:07 AM, Chet Ramey wrote:
> I guess I see what you're saying: that bash removes the backslash quoting
> the `?' when processing $'...' but leaves backslashes escaping other
> characters not listed in the description of $'...' unchanged. I can add
> that to the documentation.
Maybe OT, but there is software to hook exec at the system library level
and provide syslog auditing: https://github.com/renard/snoopylogger
-Jonathan Hankins
On Thu, Sep 3, 2015 at 2:43 PM, Chet Ramey wrote:
> On 9/3/15 2:43 AM, Ondrej Oprala wrote:
>
> > We have recently had a customer reques
