From owner-freebsd-current Sun Sep 20 04:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08590 for freebsd-current-outgoing; Sun, 20 Sep 1998 04:36:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hen.scotland.net ([194.247.65.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08433 for ; Sun, 20 Sep 1998 04:35:12 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from e2c6p29.scotland.net ([148.176.237.93] helo=timog.prestel.co.uk) by hen.scotland.net with esmtp (Exim 1.90 #5) for current@freebsd.org id 0zKhjo-0001lv-00; Sun, 20 Sep 1998 12:33:09 +0100 Received: (qmail 1138 invoked by uid 1002); 19 Sep 1998 19:43:55 -0000 Message-ID: <19980919204355.A1081@prestel.co.uk> Date: Sat, 19 Sep 1998 20:43:55 +0100 From: Timo Geusch To: current@FreeBSD.ORG Subject: Re: DEVFS & SLICE? References: <19980915094251.B204@prestel.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19980915094251.B204@prestel.co.uk>; from Timo Geusch on Tue, Sep 15, 1998 at 09:42:51AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all that replied with suggestions about what I did wrong. Problem turned out to be that I was running an initially empty /dev (which worked great with SLICE, btw). Of course a non-SLICE kernel would blow sky high... I also got the point that I should've read cvs-all. However, I really would've appreciated if Soeren would have warned the 'current' audience about the upcoming removal of the SLICE code. Timo, who is happy again that his CURRENT box is running and that the kernel page fault he was debugging turned out to be SLICE related. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message