If a core Wireshark developer repeatedly can't remember that the
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Sun, 28 Jul 2013 21:12:07 +0000 (21:12 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Sun, 28 Jul 2013 21:12:07 +0000 (21:12 +0000)
commita92a4221589a8f923930f579809da37930ba6465
tree8232de5a3f542b692b883fcf0f057b0f2a0e7af5
parent283a387c2a889f82ef6aa44167e28afa236e9195
If a core Wireshark developer repeatedly can't remember that the
argument to the -F flag for pcap format is "libpcap", not "pcap", we
have a problem.  Make it "pcap", and add a backwards-compatibility hack
to support using "libpcap" as well.

Update the man pages to refer to it as pcap as well, and fix the
capitalization of "WinPcap" (see http://www.winpcap.org) while we're at
it.

Also, refer to http://www.tcpdump.org/linktypes.html for the list of
link-layer header types for pcap and pcap-ng.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@50989 f5534014-38df-0310-8fa8-9805f1628bb7
doc/dumpcap.pod
doc/editcap.pod
doc/mergecap.pod
doc/randpkt.pod
doc/rawshark.pod
doc/text2pcap.pod
doc/tshark.pod
doc/wireshark.pod.template
wiretap/file_access.c