The following reply was made to PR port-sun3/33720; it has been noted by GNATS.

From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
To: SigmFSK@aol.com
Cc: gnats-bugs@NetBSD.org, port-sun3-maintainer@NetBSD.org,
	gnats-admin@NetBSD.org, tsutsui@ceres.dti.ne.jp
Subject: Re: port-sun3/33720: COMPAT_SUNOS kernel option not enabled by default
	 on Net...
Date: Wed, 14 Jun 2006 19:06:19 +0900

 SigmFSK@aol.com wrote:
 
 > 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.
 
 You can see differences between GENERIC and INSTALL by config files,
 sys/arch/sun3/conf/{GENERIC,INSTALL}. One reason why install.md script
 installs INSTALL kernel may be that GENERIC won't boot on some less memory
 machines (like 3/50 with 4MB RAM), but not sure.
 
 > The /netbsd kernel did NOT have any "sunos" symbols shown by nm, but  
 > rebuilding the kernel showed them (and COMPAT_SUNOS worked).
 
 You can see the running kernel name in kernel log by dmesg(8)
 or output of "uname -v". Could you check again if the GENERIC
 binary in 3.0 actually has a problem on COMPAT_SUNOS?
 ---
 Izumi Tsutsui