Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: od Date: Tue, 19 Feb 2002 13:46:25 -0500 Message-ID: <6EB31774D39507408D04392F40A10B2BC1FF42@FDYEXC202.mgroupnet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: od Thread-Index: AcG5dbtwtVE5hWw9TiS5HI30beEFFw== From: "Roth, Kevin P." To: "David" , "Mark Himsley" Cc: X-OriginalArrivalTime: 19 Feb 2002 18:46:26.0239 (UTC) FILETIME=[BC2BE4F0:01C1B975] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g1JJJtV22915 David - I agree with you that the little-endian representation can be somewhat confusing; however, as Mark pointed out, it's not likely to ever change... I've had my own "struggles" with od's idea of output formats, and have come up with a few options along the way. Here's some that will help, if you're looking to get hex characters output in the order you're expecting: $ od -toC -tc -tx1 filename 110 124 124 120 012 H T T P \n 48 54 54 50 0a $ od -tcx1 -w24 filename | sed '/^[0-9]/s/ \( .\)/\1/g'; H T T P \n 48 54 54 50 0a $ od -txlz filename 48 54 54 50 0a >HTTP.< --Kevin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/