Maybe i can clear this up:

Originally, UNIX commands had only one-character options, some of which could take an argument. The options were introduced with a dash ("-") to distinguish them from arguments, but it is possible to group such options behind a single dash. The following lines are equivalent:

Code:

command -a -b -c
command -ab -c
command -abc

The rules for interpreting the command line are implemented in a system call, getopts(), which every program should use. There is also a command getopts, which can be used to build shell scripts using the same mechanism and rule set. See man getopts for details.

(Corollary: the difference between an "option" and an "argument" is that the option changes the way the invoked command works, while arguments are input data. This is why the dash is necessary. command -abc abc will invoke option a, option b and option c, then pass "abc" as data to the invoked command.)

Now, the GNU initiative formed and they thought that one-character-options are quite unintuitive. They sought to improve on this and came up with the "long options". These are real words (like "--version", instead of "-v") and the idea was that they are easier to remember and more intuitive to understand.

Alas, this led to a problem: long options could not be introduced by a single dash like the classical options, because there would be no way to distinguish between grouped options and long options. Consider this:

Code:

command -file

should this be interpreted as invoke command with options "f", "i", "l" and "e" or should it mean invoke command with long option "file"?

Therefore the double-dash were created, which introduces long options. Single long options, because they cannot be grouped like the traditional options they were aimed to replace. So, the ambiguity above would be alleviated by:

Code:

command -file
command --file

The first means 4 single-char options, "f", "i", "l" and "e" and the second means one single long option.

Most GNU-commands (and third-party products adopting their idea) understand both variants and for most (or even all) of the long options there are single-character equivalents. In your case

Code:

uvscan -v
uvscan --version

will probably yield the same results.

I hope this helps.

bakunin