Bug 41110

Summary: "apropos linux" doesn't find brandelf
Product: Documentation Reporter: rdm <rdm>
Component: Books & ArticlesAssignee: Hiten Pandya <hmp>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description rdm 2002-07-29 08:40:04 UTC
	I recently tried to run a Linux binary on my FreeBSD 4.5
	system, getting the following nastygram:

	  ELF binary type "0" not known.
          Abort trap

	Using file(1) on the binary, I got:

          ELF 32-bit LSB executable, Intel 80386, version 1, statically 

        I tried an "apropos linux" with no success, and had to be
        bailed out by someone on freebsd-questions.

Fix: 

One possible fix would be to expand the brandelf "NAME" line:

	  brandelf - mark an ELF binary for a specific ABI (eg, Linux)

        A more general solution would be to add a "linux" page (eg, in
        section 7), talking about known issues with Linux compatibility
        mode, etc.
How-To-Repeat: 
	% apropos linux
Comment 1 John Baldwin freebsd_committer freebsd_triage 2002-07-29 13:14:35 UTC
On 29-Jul-2002 Rich Morin wrote:
> 
>>Number:         41110
>>Category:       docs
>>Synopsis:       "apropos linux" doesn't find brandelf
>>Confidential:   no
>>Severity:       non-critical
>>Priority:       low
>>Responsible:    freebsd-doc
>>State:          open
>>Quarter:        
>>Keywords:       
>>Date-Required:
>>Class:          doc-bug
>>Submitter-Id:   current-users
>>Arrival-Date:   Mon Jul 29 00:40:04 PDT 2002
>>Closed-Date:
>>Last-Modified:
>>Originator:     Rich Morin
>>Release:        FreeBSD 4.5-RELEASE i386
>>Organization:
> Canta Forda Computer Laboratory
>>Environment:
> 
>         FreeBSD cfcl.com 4.5-RELEASE FreeBSD 4.5-RELEASE #0:
>         Mon Jan 28 14:31:56 GMT 2002
>         murray@builder.freebsdmall.com:/usr/src/sys/compile/GENERIC  i386
> 
>>Description:
> 
>       I recently tried to run a Linux binary on my FreeBSD 4.5
>       system, getting the following nastygram:
> 
>         ELF binary type "0" not known.
>           Abort trap
> 
>       Using file(1) on the binary, I got:
> 
>           ELF 32-bit LSB executable, Intel 80386, version 1, statically 
> 
>         I tried an "apropos linux" with no success, and had to be
>         bailed out by someone on freebsd-questions.
> 
> 
>>How-To-Repeat:
> 
>       % apropos linux
> 
>>Fix:
> 
>       One possible fix would be to expand the brandelf "NAME" line:
> 
>         brandelf - mark an ELF binary for a specific ABI (eg, Linux)
> 
>         A more general solution would be to add a "linux" page (eg, in
>         section 7), talking about known issues with Linux compatibility
>         mode, etc.

Since brandelf can be used for OSF/1 binaries (on alpha), Solaris binaries,
etc., the more general solution is preferred. :)  linux(7) (or maybe
linux(4)) could also explain the /compat/linux magic.

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
Comment 2 simon 2003-05-26 00:22:50 UTC
Hello

FreeBSD-CURRENT has a linux(4) manual page which has never been MFC'ed.

As far as I can see linux(4) is correct for 4.X, in it's current form,
as it is for -CURRENT, so I think this PR can be solved by MFC'ing
src/share/man/man4/man4.i386/linux.4 .

Note: linux(4) references brandelf(1).

-- 
Simon L. Nielsen
Comment 3 Hiten Pandya freebsd_committer freebsd_triage 2003-09-15 01:57:10 UTC
Responsible Changed
From-To: freebsd-doc->hmp

I will take care of this once I get approval from RE team.
Comment 4 Hiten Pandya freebsd_committer freebsd_triage 2003-09-18 08:29:56 UTC
State Changed
From-To: open->closed

The linux(4) manual page has been MFC'ed.  Thanks.