summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJon Schipp <jonschipp@gmail.com>2013-11-24 15:44:47 +0100
committerTobias Klauser <tklauser@distanz.ch>2013-11-24 15:50:54 +0100
commit8dcdd694e879451d7b68e45587772757f8d7da87 (patch)
treecf36b8e22d0049eb6671b5dd21bc5ca2844f0b61
parentec90bd153699f3478e213712d7f952a21889e2ef (diff)
man: bpfc: corrected sentence by adding the word "other"
When viewing the bpfc man page I noticed a mistake saying that the BPF compiler included in the pcap library is the *only* compiler. I changed it to say the *only other* compiler since bpfc is also a BPF compiler. Signed-off-by: Jon Schipp <jonschipp@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
-rw-r--r--bpfc.84
1 files changed, 2 insertions, 2 deletions
diff --git a/bpfc.8 b/bpfc.8
index c65fbec..5661ccb 100644
--- a/bpfc.8
+++ b/bpfc.8
@@ -29,8 +29,8 @@ space for further analysis first. Meanwhile, BPF constructs also find
application in other areas such as in the communication between user and
kernel space like system call sand-boxing.
.PP
-At the time of writing this man page, the only available BPF compiler is
-part of the pcap(3) library and accessible through a high-level filter
+At the time of writing this man page, the only other available BPF compiler
+is part of the pcap(3) library and accessible through a high-level filter
language that might be familiar to many people as tcpdump-like filters.
.PP
However, it is quite often useful to bypass that compiler and write