From owner-freebsd-current Tue Sep 15 16:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03313 for freebsd-current-outgoing; Tue, 15 Sep 1998 16:16:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03296 for ; Tue, 15 Sep 1998 16:16:44 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA20081; Tue, 15 Sep 1998 16:16:18 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 15 Sep 1998 16:16:17 -0700 (PDT) From: Doug White To: Timo Geusch cc: current@FreeBSD.ORG Subject: Re: DEVFS & SLICE? In-Reply-To: <19980915094251.B204@prestel.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Sep 1998, Timo Geusch wrote: > Reply-To: > After cvsupping yesterday (2300 BST, to be exact), config(8) does not recognize > 'option SLICE' anymore. Unfortunately, removing SLICE from my config file > stops the newly created kernel dead at the point where it switches the root > device to the hard drive (yes, I checked that it is switching to the correct > device). > For the moment, it's back to booting an older kernel now, but the questions > that remain are: > - Did somebody accidentally nuke the SLICE option? No, someone intentionally nuked SLICE so it's out of the way for 3.0-RELEASE. > - Did I miss something here? Presumably, although I carefully check my archive > of 'current' (Yes, all 40Megs of it). It was noted in cvs-all. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message