Re: [Netatalk-devel] addump

[Frank L. <fra...@go...>]

2009/12/23 HAT <ha...@fa...>:
>> Unfortunately this version doesn't print anymore dev/ino/cnid/did ?!
>
> Entry ID   : 80444556 : dev (Netatalk Extended)
> Offset     : 000002C9 : 713
> Length     : 00000008 : 8
> 00000000   : 02 08 00 00 00 00 00 00                         : ........
>
> Entry ID   : 80494E4F : inode (Netatalk Extended)
> Offset     : 000002D1 : 721
> Length     : 00000008 : 8
> 00000000   : D3 16 08 00 00 00 00 00                         : ........
>
> Entry ID   : 8053594E : DB stamp (Netatalk Extended)
> Offset     : 000002D9 : 729
> Length     : 00000008 : 8
> 00000000   : DD C6 BB 4A 00 00 00 00                         : ...J....
>
> Entry ID   : 8053567E : CNID (Netatalk Extended)
> Offset     : 000002E1 : 737
> Length     : 00000004 : 4
> 00000000   : 00 00 2D 7E                                     : ..-~
>
>
> Is this insufficient?

Yes. These are plain hexdumps, which eg on x86 are in the wrong byte order.

I want:
dev/inode: printf format 0x%16x in the correct byte-order
cnid/did: printf fomat 0x%08x in the correct byte-order

dev/inode are stored in host byte-order in the files, while cnid/did
are in network byte-order.