From owner-freebsd-current  Wed May  8 20:11:45 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA02694
          for current-outgoing; Wed, 8 May 1996 20:11:45 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA02689
          for <freebsd-current@FreeBSD.org>; Wed, 8 May 1996 20:11:40 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id NAA04602; Thu, 9 May 1996 13:06:15 +1000
Date: Thu, 9 May 1996 13:06:15 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199605090306.NAA04602@godzilla.zeta.org.au>
To: ejc@nasvr1.cb.att.com, marxx@apocalypse.superlink.net
Subject: Re: -current not booting
Cc: freebsd-current@FreeBSD.org
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>	It's the SYSV* options that are making your kernel reboot at load.
>I haven't narrowed it down to which specifically on my system, but I 
>tried to configure it only with SYSVSHM, X likes it, and just that one 
>made it reboot.

sysv_shm.c was broken between 96/05/02 07:21:17 and 96/05/05 06:53:49
but I didn't notice any problems booting.

>> 	The last bootable -current kernel I have is from May 2nd.
>> A kernel from may 3,4,5,6,7 loads but does not boot, it just reboots.

Hmm.

Bruce