From owner-freebsd-current  Sun Jul  5 09:46:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA21150
          for freebsd-current-outgoing; Sun, 5 Jul 1998 09:46:13 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21142
          for <current@FreeBSD.ORG>; Sun, 5 Jul 1998 09:46:10 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA06364;
	Mon, 6 Jul 1998 02:46:00 +1000
Date: Mon, 6 Jul 1998 02:46:00 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199807051646.CAA06364@godzilla.zeta.org.au>
To: mike@smith.net.au, netchild@wurzelausix.cs.uni-sb.de
Subject: Re: Kernel panic, solved! + question
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> I've solved my problem, I had
>> config          kernel  swap on generic
>> in my kernel, after changing it to
>> config		kernel root on sd0s2
>> the new kernel bootet without a panic.
>> 
>> Q: Why did my old kernel boot, and the new one didn't?
>
>'on generic' is Evil.

I always use it.  It works fine, but has no effect unless you boot
with -a or the kernel can't find a root device in the normal way
(when it would panic outside of setconf()).  Are you using any
other nonstandard options?

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message