Sponsored Content
Top Forums Shell Programming and Scripting When comparing binary files, show human readable result? Post 303043371 by RudiC on Sunday 26th of January 2020 02:34:01 PM
Old 01-26-2020
How about
Code:
cmp -bl file[12] | awk '{LSTR = LSTR $3; RSTR = RSTR $5} END {print "left: ", LSTR; print "right:", RSTR}'
left:  69360bac2b3b7af4a4a67f6962
right: e1ccb4ce590a49a5905c05dc86

Unfortunately, this does not display the hyphens as they are identical in both files.


EDIT: alternatively, try

Code:
diff <(strings file1) <(strings file2)
12c12
< *69a3604b-ac2b-43b7-af84-0a4a67fc6962
---
> *e1accb44-ce59-40a4-9a85-0905c05cdc86

this might suffer if UTF-8 chars greater than 127 are close / around the strings of interest...


EDIT: or


Code:
cmp -bl file[12] | awk 'NR == 1 {OUT = sprintf ("xxd -pc1 -s%d ", X = $1 - 1)} END {OUT = OUT sprintf ("-l%d file", $1 - X); print OUT "1"; print "printf \"0A\n\""; print OUT "2"; print "printf \"0A\n\""}' | sh | xxd -p -r
69a3604b-ac2b-43b7-af84-0a4a67fc6962
e1accb44-ce59-40a4-9a85-0905c05cdc86


Last edited by RudiC; 01-26-2020 at 04:03 PM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

formatting output in human readable numbers

Hi, The following command provides the usage in 1024-byte blocks du -ks * | sort -n | echo "$1" ... 1588820 user10 2463140 user11 2464096 user12 5808484 user13 6387400 user14 ..... I am trying to produce an output of first coulmn by multiplying by 1024 so that the output should... (11 Replies)
Discussion started by: ghazi
11 Replies

2. Shell Programming and Scripting

script to convert epoch into human-readable

This is what I have to start out with more file 1208217600 1208131200 1193806800 I want to convert the epoch column into a human-readable format. My file has hundreds of these epoch times that I want to loop through and convert. (The epoch time is really the last column of the line) ... (3 Replies)
Discussion started by: snoman1
3 Replies

3. UNIX for Dummies Questions & Answers

How to make user's qutoa in human readable format?

$ quota Disk quotas for user cqlouis (uid 1254): Filesystem blocks quota limit grace files quota limit grace /dev/sdb1 64 300000 320000 8 0 0 $ I want to make the output of command quota in human readable format? How to? As we... (2 Replies)
Discussion started by: cqlouis
2 Replies

4. Shell Programming and Scripting

Human readable sizes in Solaris bdf

hay every body i need script like bdf -h in hp-ux there is no option like solaris df -h it is only bdf -k so i need the output with GBytes (8 Replies)
Discussion started by: maxim42
8 Replies

5. Shell Programming and Scripting

Convert epoch to human readable date & time format

Hello I have log file from solaris system which has date field converted by Java application using System.currentTimeMillis() function, example is 1280943608380 which equivalent to GMT: Wed, 04 Aug 2010 17:40:08 GMT. Now I need a function in shell script which will convert 1280943608380... (3 Replies)
Discussion started by: Yaminib
3 Replies

6. UNIX for Dummies Questions & Answers

Make netstat human readable?

Is there any way to make netstat output the information in a more human readable format? even if it's not exact? I don't even care if it has to round up/down to the nearest Meg to make it work. I wind up having to stare at netstat running for while and I wish I could get it to output things in a... (10 Replies)
Discussion started by: MrEddy
10 Replies

7. UNIX for Dummies Questions & Answers

Display Directories with their sizes in human readable format

Hi, I want to list all the directories present in a particular location and want to display their sizes as well. I know "ls -lh" but it doesn't show the size of the complete directory. So i want something like dir1 266 MB dir2 2 KB dir3 22 MB ... ... file1 10 Kb ..... Thanks Sarbjit (4 Replies)
Discussion started by: sarbjit
4 Replies

8. Shell Programming and Scripting

Making big find command more human readable

This does not work. One line works but my pattern are about 100 characters long and it is messy to read. When I try to use several lines it does not two' find "$inputDirectory" \( -name 'very long pattern1' -o -name 'very long pattern2' -o -name... (1 Reply)
Discussion started by: Michael Stora
1 Replies

9. Shell Programming and Scripting

Convert epoch time stamp into human readable format

Can someone help me to write a shell script to convert epoch timestamp into human readable format 1394553600,"test","79799776.0","19073982.728571","77547576.0","18835699.285714" 1394553600,"test1","80156064.0","19191275.014286","62475360.000000","14200554.720000"... (10 Replies)
Discussion started by: Moon1234
10 Replies

10. Programming

How to parse .nessus file to get result in human readable format?

Scripting Language: bash shell script, python I want to parse .nessus file in human readable format. If any one have any ideas please help me. (2 Replies)
Discussion started by: sk151993
2 Replies
DEBDIFF(1)						      General Commands Manual							DEBDIFF(1)

NAME
debdiff - compare file lists in two Debian packages SYNOPSIS
debdiff [options] debdiff [options] ... deb1 deb2 debdiff [options] ... changes1 changes2 debdiff [options] ... --from deb1a deb1b ... --to deb2a deb2b ... debdiff [options] ... dsc1 dsc2 DESCRIPTION
debdiff takes the names of two Debian package files (.debs or .udebs) on the command line and compares their contents (considering only the files in the main package, not the maintenance scripts). It shows which files have been introduced and which removed between the two pack- age files, and is therefore useful for spotting files which may have been inadvertently lost between revisions of the package. It also checks the file owners and permissions, and compares the control files of the two packages using the wdiff program. If no arguments are given, debdiff tries to compare the content of the current source directory with the last version of the package. debdiff can also handle changes between groups of .deb files in two ways. The first is to specify two .changes files. In this case, the .deb files listed in the .changes file will be compared, by taking the contents of all of the listed .deb files together. (The .deb files listed are assumed to be in the same directory as the .changes file.) The second way is to list the .deb files of interest specifically using the --from ... --to syntax. These both help if a package is broken up into smaller packages and one wishes to ensure that nothing is lost in the interim. debdiff examines the devscripts configuration files as described below. Command line options override the configuration file settings, though. If debdiff is passed two source packages (.dsc files) it will compare the contents of the source packages. If the source packages differ only in Debian revision number (that is, the .orig.tar.gz files are the same in the two .dsc files), then interdiff(1) will be used to com- pare the two patch files if this program is available on the system, otherwise a diff will be performed between the two source trees. OPTIONS
--dirs, -d The default mode of operation is to ignore directory names which appear in the file list, but they, too, will be considered if this option is given. --nodirs Ignore directory names which appear in the file list. This is the default and it can be used to override a configuration file set- ting. --move FROM TO, -m FROM TO It sometimes occurs that various files or directories are moved around between revisions. This can be handled using this option. There are two arguments, the first giving the location of the directory or file in the first package, and the second in the second. Any files in the first listing whose names begin with the first argument are treated as having that substituted for the second argu- ment when the file lists are compared. Any number of --move arguments may be given; they are processed in the order in which they appear. --move-regex FROM TO This is the same as --move, except that FROM is treated as a regular expression and the perl substitution command s/^FROM/TO/ is applied to the files. In particular, TO can make use of backreferences such as $1. --nocontrol debdiff will usually compare the respective control files of the packages using wdiff(1). This option suppresses this part of the processing. --control Compare the respective control files; this is the default, and it can be used to override a configuration file setting. --controlfiles FILE[,FILE ...] Specify which control files to compare; by default this is just control, but could include postinst, config and so on. Files will only be compared if they are present in both .debs being compared. The special value ALL compares all control files present in both packages, except for md5sums. This option can be used to override a configuration file setting. --wdiff-source-control When processing source packages, compare control files using wdiff. Equivalent to the --control option for binary packages. --no-wdiff-source-control Do not compare control files in source packages using wdfiff. This is the default. --wp, --wl, --wt Pass a -p, -l or -t option to wdiff respectively. (This yields the whole wdiff output rather than just the lines with any changes.) --show-moved If multiple .deb files are specified on the command line, either using .changes files or the --from/--to syntax, then this option will also show which files (if any) have moved between packages. (The package names are simply determined from the names of the .deb files.) --noshow-moved The default behaviour; can be used to override a configuration file setting. --renamed FROM TO If --show-moved is being used and a package has been renamed in the process, this command instructs debdiff to treat the package in the first list called FROM as if it were called TO. Multiple uses of this option are permitted. --exclude PATTERN Exclude files that match PATTERN. Multiple uses of this option are permitted. --diffstat Include the result of diffstat before the generated diff. --no-diffstat The default behaviour; can be used to override a configuration file setting. --auto-ver-sort When comparing source packages, do so in version order. --no-auto-ver-sort Compare source packages in the order they were passed on the command-line, even if that means comparing a package with a higher ver- sion against one with a lower version. This is the default behaviour. --unpack-tarballs When comparing source packages, also unpack tarballs found in the top level source directory to compare their contents along with the other files. This is the default behaviour. --no-unpack-tarballs Do not unpack tarballs inside source packages. --no-conf, --noconf Do not read any configuration files. This can only be used as the first option given on the command-line. --help, -h Show a summary of options. --version, -v Show version and copyright information. --quiet, -q Be quiet if no differences were found. --ignore-space, -w Ignore whitespace in diffs. CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables. Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently recognised variables are: DEBDIFF_DIRS If this is set to yes, then it is the same as the --dirs command line parameter being used. DEBDIFF_CONTROL If this is set to no, then it is the same as the --nocontrol command line parameter being used. The default is yes. DEBDIFF_CONTROLFILES Which control files to compare, corresponding to the --controlfiles command line option. The default is control. DEBDIFF_SHOW_MOVED If this is set to yes, then it is the same as the --show-moved command line parameter being used. DEBDIFF_WDIFF_OPT This option will be passed to wdiff; it should be one of -p, -l or -t. DEBDIFF_SHOW_DIFFSTAT If this is set to yes, then it is the same as the --diffstat command line parameter being used. DEBDIFF_WDIFF_SOURCE_CONTROL If this is set to yes, then it is the same as the --wdiff-source-control command line parameter being used. DEBDIFF_AUTO_VER_SORT If this is set to yes, then it is the same as the --auto-ver-sort command line parameter being used. DEBDIFF_UNPACK_TARBALLS If this is set to no, then it is the same as the --no-unpack-tarballs command line parameter being used. EXIT VALUES
Normally the exit value will be 0 if no differences are reported and 1 if any are reported. If there is some fatal error, the exit code will be 255. SEE ALSO
dpkg-deb(1), wdiff(1), interdiff(1), diffstat(1) and devscripts.conf(5). AUTHOR
debdiff was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by Julian Gilbey <jdg@debian.org>. The software may be freely redistributed under the terms and conditions of the GNU General Public License, ver- sion 2. DEBIAN
Debian Utilities DEBDIFF(1)
All times are GMT -4. The time now is 05:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy