Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA00164; Wed, 20 Dec 95 03:46:18 EST Received: from pain.lcs.mit.edu by MIT.EDU with SMTP id AA08220; Wed, 20 Dec 95 03:46:18 EST Received: (from daemon@localhost) by pain.lcs.mit.edu (8.6.12/8.6.9) id DAA19937; Wed, 20 Dec 1995 03:02:32 -0500 Received: from mail.telstra.com.au by pain.lcs.mit.edu (8.6.12/8.6.9) with ESMTP id CAA17623 for ; Wed, 20 Dec 1995 02:01:06 -0500 Received: from mail_gw.fwall.telecom.com.au(192.148.147.10) by mail via smap (V1.3) id sma016550; Wed Dec 20 11:59:23 1995 Received: from cdn_mail.dn.itg.telecom.com.au(144.135.109.134) by mail_gw.telecom.com.au via smap (V1.3) id sma009313; Wed Dec 20 17:59:22 1995 Received: from frodo.dn.itg.telecom.com.au (frodo.dn.itg.telecom.com.au [144.136.188.211]) by cdn_mail.dn.itg.telecom.com.au (8.6.11/8.6.9) with ESMTP id RAA29533; Wed, 20 Dec 1995 17:59:20 +1100 Received: from localhost (localhost [127.0.0.1]) by frodo.dn.itg.telecom.com.au (8.6.11/8.6.9) with SMTP id LAA22841; Tue, 19 Dec 1995 11:25:28 +1100 Message-Id: <199512190025.LAA22841@frodo.dn.itg.telecom.com.au> X-Authentication-Warning: frodo.dn.itg.telecom.com.au: Host localhost didn't use HELO protocol To: matthew green Cc: port-sparc@netbsd.org, Paul Kranenburg Subject: Re: Booting IPX diskless not too good... In-Reply-To: Your message of "Mon, 18 Dec 1995 18:23:52 +1100." <199512180723.SAA22898@dynamo.mame.mu.OZ.AU> Date: Tue, 19 Dec 1995 11:25:28 +1100 From: "Simon J. Gerraty" Sender: owner-port-sparc@NetBSD.ORG Precedence: list X-Loop: port-sparc@NetBSD.ORG > i'm not so sure that it is the size of the kernel here that is > the problem -- it's the fact that there are debugging symbols in > the program, possible pushing some size lossage somewhere.. Hmmm, yesterday I diff'd the nm output of the two kernels. Today I cmp'd them and they are apparently the same. MD5 (netbsd) = 5d8de24a65b422c924cd37f1d3a83b8a MD5 (netbsd.small) = 5d8de24a65b422c924cd37f1d3a83b8a So in this case, strip -d was like waving a dead chicken... I have no idea why it successfully booted after that. Sorry for the confusion. --sjg