From owner-freebsd-hackers Mon May 29 18:39:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA00561 for hackers-outgoing; Mon, 29 May 1995 18:39:23 -0700 Received: from orion.stars.sed.monmouth.army.mil ([158.9.11.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA08750 for ; Mon, 29 May 1995 15:13:27 -0700 Message-Id: <199505292213.PAA08750@freefall.cdrom.com> Received: by orion.stars.sed.monmouth.army.mil (1.37.109.16/16.2) id AA068415387; Mon, 29 May 1995 18:09:47 -0400 From: william pechter ILEX Subject: Re: Anyone built a config -g'd kernel lately? To: taob@gate.sinica.edu.tw (Brian Tao) Date: Mon, 29 May 1995 18:09:47 -0400 (EDT) Cc: FreeBSD-hackers@FreeBSD.org (FreeBSD-hackers) In-Reply-To: from "Brian Tao" at May 29, 95 02:06:34 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 602 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > On Sun, 28 May 1995, Karl Strickland wrote: > > > > I tried to build a -current kernel (src about 4 days old) with config -g, > > and it reboots almost immediately on startup, it doesnt even finish printing > > the 'text=xxxxx, data=xxxx bla bla bla' line. (I did a strip -x on the > > newly installed kernel). > > > > Building the kernel from the same sources without a '-g' option to config > > results in a kernel that works fine. Interesting -- since I have this problem only on booting from hard disk with the install disks on the entire 2.x series. Booting from floppy works ok. Bill