Subject: Re: tcpdump(8) file format on 64bit arch
To: None <email@example.com>
From: None <firstname.lastname@example.org>
Date: 06/12/2000 00:53:41
> > at this moment, netbsd-current tcpdump(8) writes out "struct timeval"
> > into packet dump file (like -w). this constitutes file incompatibility
> > between 32bit arch and 64bit arch. tcpdump.org codebase now always
> > emit 32bit timeval. Is it okay if I bring in this change?
>Hm. tcpdump.org should always emit a 64-bit timeval! They clearly
>weren't planning ahead on this one.
the reason for picking 32bit timeval is, I think, as follows:
- there are too many existing files with 32bit timeval, and
- there's no robust way to determine 32bit timeval from 64bit timeval
so we can't really read in both