hexdump manpage says nothing about output or input endianness. If this non homogeneous behaviour is not a bug, please add a note about it in the manpage.
On 6/25/08, Christoph Berg <[EMAIL PROTECTED]> wrote: > Re: Nahuel Greco 2008-01-15 <[EMAIL PROTECTED]> > > hexdump shows swapped bytes when dumping in default mode (no flags). See > > this: > > > > [EMAIL PROTECTED]:~$ echo abcd > /tmp/file > > [EMAIL PROTECTED]:~$ hexdump /tmp/file > > 0000000 6261 6463 000a > > 0000005 > > [EMAIL PROTECTED]:~$ hexdump -b /tmp/file > > 0000000 141 142 143 144 012 > > 0000005 > > [EMAIL PROTECTED]:~$ > > > > In the first dump, the bytes are swapped, in the second one, the output > > is correct. > > This is not a bug. (It's just strange, but that's how hexdump is > designed to work, think big endian.) > > Christoph > > -- > [EMAIL PROTECTED] | http://www.df7cb.de/ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFIYl4xxa93SlhRC1oRAvakAJ9ubOiB2dV1T485kLpp84yedsQZGQCgr26+ > 9b8SqhRv7b9KxlxQL0ZHHXs= > =Iw3W > -----END PGP SIGNATURE----- > > > -- Saludos, Nahuel Greco. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
