From owner-freebsd-current Wed May 8 17:57:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA16594 for current-outgoing; Wed, 8 May 1996 17:57:59 -0700 (PDT) Received: from apocalypse.superlink.net (root@apocalypse.superlink.net [205.246.27.150]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA16588 for ; Wed, 8 May 1996 17:57:55 -0700 (PDT) Received: (from marxx@localhost) by apocalypse.superlink.net (8.7.5/8.7.3) id RAA00543; Wed, 8 May 1996 17:06:33 -0400 (EDT) Date: Wed, 8 May 1996 17:06:32 -0400 (EDT) From: "Charles C. Figueiredo" To: ejc@nasvr1.cb.att.com cc: freebsd-current@freebsd.org Subject: Re: -current not booting In-Reply-To: <9605071252.AA10462@ginger.cb.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. "I don't want to grow up, I'm a BSD kid. There's so many toys in /usr/bin that I can play with!" ------------------------------------------------------------------------------ Charles C. Figueiredo Marxx marxx@superlink.net ------------------------------------------------------------------------------ On Tue, 7 May 1996 ejc@nasvr1.cb.att.com wrote: > Hello > 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. > > Does anybody know what broke? > > ejc > > Lucent >