- libxt_bpf: use correct shell term in man page description
PATCH 1/1 - libxt_bpf: use correct shell term in man page description
Hello,
use 'command substitution' as correct shell term instead of 'backticks'. Also mention backquotes and `$()' form.
btw: After compiling in the git directory the nfbpf_compile binary is shown as new file by git. Should that be so?
Best regards
Mart
Quoted 1 line
From
536c34c67b4149e7c83f474350d8a5fbaaa0fa6dMon Sep 17 00:00:00 2001
From: Mart Frauenlob <[email protected]>
Date: Mon, 8 Apr 2013 10:03:22 +0200
Subject: [PATCH] libxt_bpf.man: Use correct shell term in man page.
--- extensions/libxt_bpf.man | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
extensions/libxt_bpf.man +1 -1
@@ -2,7 +2,7 @@ Match using Linux Socket Filter. Expects a BPF program in decimal format. This is the format generated by the \fBnfbpf_compile\fP utility. .TP \fB\-\-bytecode\fP \fIcode\fP -Pass the code in backtick format as argument. +Pass the code as argument using command substitution (backquotes or `$()' form). .PP The code format is similar to the output of the tcpdump -ddd command: one line that stores the number of instructions, followed by one line for each
Signature · 1 line
1.7.2.5
Quoted 4 lines · Mart Frauenlob
Hello,
use 'command substitution' as correct shell term instead of 'backticks'. Also mention backquotes and `$()' form.
I have applied this change to clarify this:
extensions/libxt_bpf.man +0 -0
@@ -2,7 +2,7 @@ Match using Linux Socket Filter. Expects a BPF program
in decimal format. This
is the format generated by the \fBnfbpf_compile\fP utility.
.TP
\fB\-\-bytecode\fP \fIcode\fP
-Pass the code in backtick format as argument.
+Pass the BPF bytes code format (described in the example below).
.PP
The code format is similar to the output of the tcpdump -ddd command: one line that stores the number of instructions, followed by one line for each
Quoted 2 lines
btw: After compiling in the git directory the
nfbpf_compilebinary is shown as new file by git. Should that be so?
I have also fixed this.
Regards.