Re: Which version of FreeBSD a binary was compiled for?

2005-10-28 Thread Andrew P.
On 10/28/05, Micah [EMAIL PROTECTED] wrote: David Kirchner wrote: On 10/27/05, Will Maier [EMAIL PROTECTED] wrote: Must be -- some flag produces unique bits in the executables. I'm a little surprised there isn't (AFAICT) anything descriptive in file(1)'s manpage or /u/s/mi/magic that would

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread Andrew P.
On 10/27/05, Joshua Tinnin [EMAIL PROTECTED] wrote: On Wed 26 Oct 05 09:18, Andrew P. [EMAIL PROTECTED] wrote: On 10/26/05, Robert Huff [EMAIL PROTECTED] wrote: Andrew P. writes: file /usr/bin/man on my machine outputs: /usr/bin/man: ELF 32-bit LSB executable,

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread Micah
Andrew P. wrote: On 10/27/05, Joshua Tinnin [EMAIL PROTECTED] wrote: On Wed 26 Oct 05 09:18, Andrew P. [EMAIL PROTECTED] wrote: On 10/26/05, Robert Huff [EMAIL PROTECTED] wrote: Andrew P. writes: file /usr/bin/man on my machine outputs: /usr/bin/man: ELF 32-bit LSB executable, Intel

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread Will Maier
On Thu, Oct 27, 2005 at 06:51:21AM -0700, Micah wrote: I have a 5.4 system, /do/ go into single user when upgrading, and file does /not/ report FreeBSD version. I get the same output you do. It would be nice to know why this works on some systems and not on others. Consider diff'ing the

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread Micah
Will Maier wrote: On Thu, Oct 27, 2005 at 06:51:21AM -0700, Micah wrote: I have a 5.4 system, /do/ go into single user when upgrading, and file does /not/ report FreeBSD version. I get the same output you do. It would be nice to know why this works on some systems and not on others.

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread Micah
Will Maier wrote: On Thu, Oct 27, 2005 at 06:51:21AM -0700, Micah wrote: I have a 5.4 system, /do/ go into single user when upgrading, and file does /not/ report FreeBSD version. I get the same output you do. It would be nice to know why this works on some systems and not on others.

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread Will Maier
On Thu, Oct 27, 2005 at 11:36:18AM -0700, Micah wrote: In other words, it's not file that broken, but /every/ executable on the broken machine is broken. Now why would that be? A compiler flag or something? Must be -- some flag produces unique bits in the executables. I'm a little surprised

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread David Kirchner
On 10/27/05, Will Maier [EMAIL PROTECTED] wrote: Must be -- some flag produces unique bits in the executables. I'm a little surprised there isn't (AFAICT) anything descriptive in file(1)'s manpage or /u/s/mi/magic that would explain the discrepancy. Didn't see anything in quick looks through

Re: Which version of FreeBSD a binary was compiled for?

2005-10-27 Thread Micah
David Kirchner wrote: On 10/27/05, Will Maier [EMAIL PROTECTED] wrote: Must be -- some flag produces unique bits in the executables. I'm a little surprised there isn't (AFAICT) anything descriptive in file(1)'s manpage or /u/s/mi/magic that would explain the discrepancy. Didn't see anything in

Re: Which version of FreeBSD a binary was compiled for?

2005-10-26 Thread Andrew P.
On 10/26/05, Will Maier [EMAIL PROTECTED] wrote: On Wed, Oct 26, 2005 at 02:24:54AM +0400, Andrew P. wrote: How to tell? Apart from trying to launch it on different versions without COMPAT* in the kernel? file (1) I don't mean to push it, but how file would ever help me to know subj?

Re: Which version of FreeBSD a binary was compiled for?

2005-10-26 Thread Michael C. Shultz
On Wednesday 26 October 2005 00:01, Andrew P. wrote: On 10/26/05, Will Maier [EMAIL PROTECTED] wrote: On Wed, Oct 26, 2005 at 02:24:54AM +0400, Andrew P. wrote: How to tell? Apart from trying to launch it on different versions without COMPAT* in the kernel? file (1) I don't mean to

Re: Which version of FreeBSD a binary was compiled for?

2005-10-26 Thread Andrew P.
On 10/26/05, Michael C. Shultz [EMAIL PROTECTED] wrote: On Wednesday 26 October 2005 00:01, Andrew P. wrote: On 10/26/05, Will Maier [EMAIL PROTECTED] wrote: On Wed, Oct 26, 2005 at 02:24:54AM +0400, Andrew P. wrote: How to tell? Apart from trying to launch it on different versions

Re: Which version of FreeBSD a binary was compiled for?

2005-10-26 Thread Robert Huff
Andrew P. writes: file /usr/bin/man on my machine outputs: /usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.4-CURRENT (rev 3), dynamically linked (uses shared libs), stripped Oh, it's just that file hasn't leared anything about

Re: Which version of FreeBSD a binary was compiled for?

2005-10-26 Thread Andrew P.
On 10/26/05, Robert Huff [EMAIL PROTECTED] wrote: Andrew P. writes: file /usr/bin/man on my machine outputs: /usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.4-CURRENT (rev 3), dynamically linked (uses shared libs), stripped

Re: Which version of FreeBSD a binary was compiled for?

2005-10-26 Thread Joshua Tinnin
On Wed 26 Oct 05 09:18, Andrew P. [EMAIL PROTECTED] wrote: On 10/26/05, Robert Huff [EMAIL PROTECTED] wrote: Andrew P. writes: file /usr/bin/man on my machine outputs: /usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD

Which version of FreeBSD a binary was compiled for?

2005-10-25 Thread Andrew P.
How to tell? Apart from trying to launch it on different versions without COMPAT* in the kernel? One can always carefully examine the output of ldd, readelf and other such tools, but that requires much knowledge and a small lab with all kinds of BSD's set up. Is there a better way?

Re: Which version of FreeBSD a binary was compiled for?

2005-10-25 Thread Will Maier
On Wed, Oct 26, 2005 at 02:24:54AM +0400, Andrew P. wrote: How to tell? Apart from trying to launch it on different versions without COMPAT* in the kernel? file (1) One can always carefully examine the output of ldd, readelf and other such tools, but that requires much knowledge and a small