On Fri, Jul 06, 2001 at 12:04:39AM -0700, Ian Lance Taylor wrote:
>Arjen van Drie <[EMAIL PROTECTED]> writes:
>
>> On Thu, Jul 05, 2001 at 11:21:10PM +0200, Peter van Dijk wrote:
>> >
>> >Could you show us a hexdump of that file? This is interesting :)
>>
>> 0000000 2123 622f 6e69 732f 0a68 7865 6365 2f20
>> 0000010 7375 2f72 6f6c 6163 2f6c 6962 2f6e 6374
>> 0000020 7370 7265 6576 2072 782d 2f20 7465 2f63
>> 0000030 6374 7270 6c75 7365 642e 742f 7063 702e
>> 0000040 706f 2e33 6463 2062 762d 2d20 2052 482d
>> 0000050 2d20 206c 2030 2030 3131 2030 0a5c 2f09
>> 0000060 6176 2f72 6d71 6961 2f6c 6962 2f6e 6d71
>> 0000070 6961 2d6c 6f70 7570 2070 6469 2e73 7274
>> 0000080 7669 6169 2e6c 7633 2e61 656e 2074 622f
>> 0000090 6e69 632f 6568 6b63 6170 7373 6f77 6472
>> 00000a0 5c20 0a20 2f09 6176 2f72 6d71 6961 2f6c
>> 00000b0 6962 2f6e 6d71 6961 2d6c 6f70 3370 2064
>> 00000c0 614d 6c69 6964 2072 3e32 3126 0a0a
>> 00000ce
>
>There is a space after the second backslash. This means that the
>backslash is not a line continuation character, since that only
>happens if the backslash appears at the end of the line. That means
>that checkpassword is being run with no arguments, which causes it to
>silently and immediately exit.
>
>You will see this if you use `cat -ve' on the file.
Thanks all. It works now. How does one read hexdumps? Is there
a howto or a table somewhere?
--
Grtz,
Arjen.
