From owner-freebsd-bugs Mon May 10 1:23:55 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 67C94156FA; Mon, 10 May 1999 01:23:51 -0700 (PDT) (envelope-from wefa@callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id KAA12399; Mon, 10 May 1999 10:23:45 +0200 (CEST) Received: from kassandra.otelo-call.de(194.233.120.15) by custos.otelo-call.de via smap (V2.1) id xma012397; Mon, 10 May 99 10:23:39 +0200 Received: from otc.otelo-call.de (otc.otelo-call.de [194.233.120.22]) by kassandra.otelo-call.de (8.8.5/8.8.5) with ESMTP id KAA05144; Mon, 10 May 1999 10:23:39 +0200 (CEST) Received: from OTC/SpoolDir by otc.otelo-call.de (Mercury 1.31); 10 May 99 10:23:39 +0100 Received: from SpoolDir by OTC (Mercury 1.31); 10 May 99 10:23:17 +0100 From: "Christoph Weber-Fahr" Organization: O.tel.o Communications GmbH To: dcs@FreeBSD.org, freebsd-bugs@FreeBSD.org Date: Mon, 10 May 1999 10:23:14 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: kern/11357: unable to record kernel -c changes (yes!) In-reply-to: <199905080428.VAA15804@freefall.freebsd.org> X-mailer: Pegasus Mail for Windows (v2.54) Message-ID: <36563744459B@otc.otelo-call.de> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 7 May 99 , 21:28 you wrote: > Synopsis: unable to record kernel -c changes (yes!) > > State-Changed-From-To: open->closed > State-Changed-By: dcs > State-Changed-When: Fri May 7 21:26:11 PDT 1999 > State-Changed-Why: > Kget's error message is just an inconsequential warning. > kget >/boot/kernel.conf will work even if it displays that message. Obviously it does ... but this is not the problem I reported, just some hint on a possible source of it. The problem is: unable to record kernel -c changes If it worked as advertized, kernel -c changes would get written back somewhere automatically, even if that somewhere is, as documented in ERRATA.TXT, not the place it should be. In my system they don't get written back at all. This problem is actually here, verifiable, repeatable. If you need more information on this, please tell me. So, could you, please, at least reopen that PR ? Regards, Christoph Weber-Fahr ________________________________________________________ Christoph Weber-Fahr wefa@callcenter.systemhaus.net O.tel.o Communications GmbH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message