From owner-freebsd-current Fri Nov 10 18:38: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3EBB437B479; Fri, 10 Nov 2000 18:38:01 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA22662; Fri, 10 Nov 2000 18:38:00 -0800 Date: Fri, 10 Nov 2000 18:37:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: savecore broken because kern.bootfile is set wrong In-Reply-To: <200011110237.eAB2bw909143@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, things are more broken than I thought. The -current loader for alpha is passing "kernel" in the bootinfo structure- not the full pathname. Loader bug. What's amusing is that kenv does see a full pathname. So, now why did the lines below fail to see the pathname? Hmmm.. ponders.... -matt > > Something actually was changed at some point perhaps? > > On i386, kernelname is dug out of bootinfo and copied > > (in assembler). > > > > On alpha: > > > > p = getenv("kernelname"); > > if (p) > > strncpy(kernelname, p, sizeof(kernelname) - 1); > > > > > > Did the loader used to set kernelname as an environment variable? > > It should still do it. (The forth code handles this) My only Alpha is > running -stable, and $kernelname is set correctly there (see the output > of 'kenv'). > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message