At 16:08 -0600 12/19/01, Chris Devers wrote: >Good observation. I have one naked .bom file in there and 36 .pkg folders, >all of which contain a .bom file. Can't tell what any of them are though, >since /usr/bin/strings insists they aren't object files & thus won't read >them. They're clearly not ascii either though... *shrug*
You can use the "lsbom" command to view these bom files. They're just lists of what was in the .pax.gz for that package, along with file sizes, checksums, UIDs, and other information. [localhost:BSD.pkg/Contents/Resources] adam% lsbom BSD.bom .. 41775 0/80 ../Library 40775 0/80 ../Library/Documentation 40775 0/80 ../Library/Documentation/Commands 40775 0/80 ../Library/Documentation/Commands/dc 40775 0/80 ../Library/Documentation/Commands/dc/dc_1.html 100664 0/80 1820 657963583 ../Library/Documentation/Commands/dc/dc_10.html 100664 0/80 1764 1686084560 ../Library/Documentation/Commands/dc/dc_11.html 100664 0/80 804 4163743412 ../Library/Documentation/Commands/dc/dc_2.html 100664 0/80 1714 2291197100 ../Library/Documentation/Commands/dc/dc_3.html 100664 0/80 1824 3144921161 .... etc., etc. See the man pages for bom(5), lsbom(8), and mkbom(8) for more information. The bom man page describes the bom format. adam --
