[dns-operations] dnscap -> dnspcap, and some notes about ncap
Joao_Damas at isc.org
Tue Aug 21 18:05:28 UTC 2007
and now to correct myself, thanks to someone who questioned the case-
sensitiveness of DOS/WIN options, while the command name is not case
sensitive, options are and all there is is a style guide recommending
the use of one case if possible. So using -p and -P won't confuse things
On 21 Aug 2007, at 09:36, Joao Damas wrote:
> problem here is the general shortness of the alphabet.
> Paul wants to stay away from capital letter options as much as
> possible because DOS/WIN folds everything into the same case.
> -p is commonly used for promiscuous, and we are trying to not use
> capital P, -u was the less awkward choice (or so it seemed)
> -i is used in all tcpdump family tools to mean the interface, not the
> input file.
> -d is avaiable and can be used for direction
> I have no problem with using -w instead of -o (with -r for input,
> given that -i means interface), though I have seen plenty usage of
> all combinations.
> On 21 Aug 2007, at 07:03, Robert Story wrote:
>> On Mon, 20 Aug 2007 14:48:43 -0700 Joao wrote:
>> JD> And so, this is the new proposed set of command line switches
>> JD> changes) and we would like to collect any comments people might
>> JD> on them.
>> JD> -u port : TCP/UDP port to capture traffic on
>> JD> -p : promiscuous capture
>> JD> -r input file
>> I'd suggest trying to keep in line with common command line options
>> many other programs, and would change :
>> -p port : TCP/UDP port to capture traffic on
>> -i : input file
>> If the command is going to take and interface command, then maybe -i
>> would be reserved for that, in which case I'd suggest -f for input
>> Using p for port means you need something else for promiscuous, so
>> suggest :
>> -P : promiscuous capture
>> Robert Story
> dns-operations mailing list
> dns-operations at lists.oarci.net
More information about the dns-operations