NetBSD Problem Report #10837

Received: (qmail 13739 invoked from network); 15 Aug 2000 16:17:59 -0000
Message-Id: <20000815161758.15E78872@sean.ebone.net>
Date: Tue, 15 Aug 2000 18:17:58 +0200 (CEST)
From: smd@ebone.net
Reply-To: smd@ebone.net
To: gnats-bugs@gnats.netbsd.org
Subject: no COMPAT_AOUT -> "No ld.so" on one machine
X-Send-Pr-Version: 3.95

>Number:         10837
>Category:       kern
>Synopsis:       no COMPAT_AOUT -> "No ld.so" on one machine
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 15 16:18:00 +0000 2000
>Closed-Date:    Thu Nov 09 23:20:40 +0000 2000
>Last-Modified:  Thu Nov 09 23:20:40 +0000 2000
>Originator:     Sean Doran
>Release:        CVS 2000 08 15
>Organization:
Sean Doran <smd@ebone.net>
Development Manager, Ebone Inc., Copenhagen Denmark
>Environment:

System: NetBSD sean.ebone.net 1.5E NetBSD 1.5E (EBONE) #0: Tue Aug 15 16:10:27 CEST 2000 smd@sean.ebone.net:/usr/src/sys/arch/i386/compile/EBONE i386

no COMPAT_AOUT

versus

NetBSD 1.5E (SCREAM) #0: Thu Aug 10 04:03:43 CEST 2000
and
NetBSD 1.5E (NLAPTOY) #0: Sun Aug 13 22:50:51 CEST 2000

no COMPAT_AOUT


>Description:
	In the first machine, which is not really different in any
	obvious way from the other two in terms of kernel config,
	I get this:

 22484 ktrace   NAMI  "/usr/pkg/bin/setiathome"
 22484 setiathome EMUL  "netbsd"
 22484 setiathome RET   execve JUSTRETURN
 22484 setiathome CALL  open(0x10f0,0,0)
 22484 setiathome NAMI  "/usr/libexec/ld.so"
 22484 setiathome RET   open -1 errno 2 No such file or directory
 22484 setiathome CALL  write(0x2,0x1103,0xa)
 22484 setiathome GIO   fd 2 wrote 10 bytes
       "No ld.so
        \0"
 22484 setiathome RET   write 10/0xa
 22484 setiathome CALL  exit(0x1)

In the others, setiathome runs normally.  There is no "ld.so" to be found,
other than in /emul/aout/usr/libexec.

Has the absence of "options COMPAT_AOUT" not led to a COMPAT_AOUT-free
kernel in the slightly older kernels?   Or am I lost, clueless, whatever?
I'm pretty sure I did an rm -rf /sys/arch/i386/compile/{NLAPTOY,SCREAM}
before building the COMPAT_AOUT-free kernels...

Here's what one of them says:

  6504 ktrace   NAMI  "/usr/pkg/bin/setiathome"
  6504 setiathome EMUL  "netbsd"
  6504 setiathome RET   execve JUSTRETURN
  6504 setiathome CALL  open(0x10f0,0,0)
  6504 setiathome NAMI  "/emul/aout/usr/libexec/ld.so"
  6504 setiathome NAMI  "/emul/aout"
  6504 setiathome NAMI  "/emul/aout/usr/libexec/ld.so"
  6504 setiathome RET   open 3
       ...

>How-To-Repeat:
	Boot a kernel without COMPAT_AOUT on "EBONE", watch it not work.
	Boot a kernel without COMPAT_AOUT on "NLAPTOY", watch it work.
>Fix:

>Release-Note:
>Audit-Trail:

From: smd@ebone.net (Sean Doran by way of Erik E. Fair)
To: gnats-bugs@netbsd.org
Cc:  
Subject: Re: kern/10837: no COMPAT_AOUT -> "No ld.so" on one machine
Date: Thu, 7 Sep 2000 14:08:52 -0700

 This:

 # ln -s /emul/aout/usr/lib/ld.so /usr/libexec
 # exit
 : es ; env 'LD_LIBRARY_PATH=/emul/aout/usr/lib' setiathome -h

 works.

 Isn't there supposed to be some magical aout ld.so that tries /emul/aout
 first?  Or did I misread the whole thread about COMPAT_AOUT going away?

 	Sean.
State-Changed-From-To: open->closed 
State-Changed-By: martin 
State-Changed-When: Thu Nov 9 15:16:06 PST 2000 
State-Changed-Why:  
Closed on request of submitter: 
kern/10837 no longer is a problem, thanks to the shipped-uuencoded 
aout all-knowing ld.so. :-) 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.