I didn't see this appear, so forwarding it with a different subject; apologies if you get this twice - if so please let me know, and I'll investigate why I didn't see my own summary appear.... Thanks. Steve. ---------- Forwarded message ---------- From: Steve Nelson <sanelson@gmail.com> Date: Tue, 15 Mar 2005 08:39:44 +0000 Subject: [SUMMARY] Hex Editing To: sunmanagers@sunmanagers.org Thanks to the many responses - emacs was frequently recommended as the tool to use (in vip mode if you don't want to learn emacs). Also vim includes xxd, allowing you to convert the hex to and from a dump format In the specific case of wtmpx, the following tools and links were most helpful: /usr/lib/acct/fwtmp [-ic] /usr/lib/acct/wtmpfix [file...] http://docs.sun.com/app/docs/doc/816-0211/6m6nc66rf?a=view http://docs.sun.com/app/docs/doc/806-4074/6jd68pq02?a=view Dedicated editors were also recommended, including: bvi - bvi.sourceforge.net bed (binary editor) - ftp://ftp.uu.net/usenet/comp.sources.unix/volume1/ Other suggestions were to use strings, and od: Two useful options: -x to dump bytes as hex rather than octal -c to print the ascii representation for byte values 0-127. The general feeling was that few of the built-in editors will make sense of a binary file - they don't generally know how to handle bytes with the high bit set (128 to 255, or -128 to -1 in "signed speak"). Thanks very much for the detailed and quick responses. Steve Nelson _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Mar 17 02:18:20 2005
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:44 EST