Subject: Re: port-sun3/33720: COMPAT_SUNOS kernel option not enabled by default on Net...
To: None <port-sun3-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: None <SigmFSK@aol.com>
List: netbsd-bugs
Date: 06/14/2006 02:50:03
The following reply was made to PR port-sun3/33720; it has been noted by GNATS.

From: SigmFSK@aol.com
To: gnats-bugs@NetBSD.org, port-sun3-maintainer@netbsd.org,
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc: 
Subject: Re: port-sun3/33720: COMPAT_SUNOS kernel option not enabled by default on Net...
Date: Tue, 13 Jun 2006 22:47:53 EDT

 -------------------------------1150253273
 Content-Type: text/plain; charset="US-ASCII"
 Content-Transfer-Encoding: 7bit
 
  
 In a message dated 6/13/2006 7:45:32 P.M. Eastern Standard Time,  
 tsutsui@ceres.dti.ne.jp writes:
 
 sigmfsk@aol.com wrote:
 
 > After loading NetBSD 3.0 on a Sun3,  attempting to run a SunOS
 > executable produces the message: Exec format  error. Wrong Architecture.
 
 Are you sure you are really using  GENERIC?
 I guess install.md script install INSTALL kernel (which is in  miniroot)
 to your disk, not GENERIC by default.
 
 You can check  GENERIC kernel binary by nm(1) if it contains
 any "sunos" symbols, and  ktrace(1) also may help to check
 how the binary fails.
 ---
 Izumi  Tsutsui
 
 Hi Izumi:
 Good thinking.  I don't know if the kernel that was left in /netbsd  after 
 the install was the INSTALL kernel or the GENERIC kernel.  Everything  worked 
 other than running SunOS executables.
  
 The /netbsd kernel did NOT have any "sunos" symbols shown by nm, but  
 rebuilding the kernel showed them (and COMPAT_SUNOS worked).
  
 I'm new to NetBSD; let me know if there's anything I can check or do here  
 with my disk image.
  
 thanks,
 arthur
 
 -------------------------------1150253273
 Content-Type: text/html; charset="US-ASCII"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META http-equiv=3DContent-Type content=3D"text/html; charset=3DUS-ASCII">
 <META content=3D"MSHTML 6.00.5296.0" name=3DGENERATOR></HEAD>
 <BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
 Arial"=20
 bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
 e_document=20
 face=3DArial color=3D#000000 size=3D2>
 <DIV>
 <DIV>In a message dated 6/13/2006 7:45:32 P.M. Eastern Standard Time,=20
 tsutsui@ceres.dti.ne.jp writes:</DIV>
 <BLOCKQUOTE=20
 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
 FONT=20
   style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
   size=3D2>sigmfsk@aol.com wrote:<BR><BR>&gt; After loading NetBSD 3.0 on a=20=
 Sun3,=20
   attempting to run a SunOS<BR>&gt; executable produces the message: Exec fo=
 rmat=20
   error. Wrong Architecture.<BR><BR>Are you sure you are really using=20
   GENERIC?<BR>I guess install.md script install INSTALL kernel (which is in=20
   miniroot)<BR>to your disk, not GENERIC by default.<BR><BR>You can check=20
   GENERIC kernel binary by nm(1) if it contains<BR>any "sunos" symbols, and=20
   ktrace(1) also may help to check<BR>how the binary fails.<BR>---<BR>Izumi=20
   Tsutsui</FONT></BLOCKQUOTE></DIV>
 <DIV>Hi Izumi:</DIV>
 <DIV>Good thinking.&nbsp; I don't know if the kernel that was left in /netbs=
 d=20
 after the install was the INSTALL kernel or the GENERIC kernel.&nbsp; Everyt=
 hing=20
 worked&nbsp;other than running SunOS executables.</DIV>
 <DIV>&nbsp;</DIV>
 <DIV>The /netbsd kernel did NOT have any "sunos" symbols shown by nm, but=20
 rebuilding the kernel showed them (and COMPAT_SUNOS worked).</DIV>
 <DIV>&nbsp;</DIV>
 <DIV>I'm new to NetBSD; let me know if there's anything I can check or do he=
 re=20
 with my disk image.</DIV>
 <DIV>&nbsp;</DIV>
 <DIV>thanks,</DIV>
 <DIV>arthur</DIV></FONT></BODY></HTML>
 
 -------------------------------1150253273--