From owner-freebsd-current Sat Oct 5 10:33:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A95E37B401 for ; Sat, 5 Oct 2002 10:33:17 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0B9E43E65 for ; Sat, 5 Oct 2002 10:33:16 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g95HWnOo097819 for ; Sat, 5 Oct 2002 13:32:49 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 5 Oct 2002 13:32:48 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Subject: HEADS UP: options GEOM/NO_GEOM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In case you are foolishly tracking -current without reading the CVS logs, you might want to be aware that the default just changed such that you get GEOM unless you explicitly specify NO_GEOM in your kernel configuration file. The pre-defined kernel configs in the base tree all specify NO_GEOM, so if you're just tracking GENERIC, you'll get the same non-GEOM behavior you had before. If you're using a custom kernel config and don't want GEOM, you'll need to add NO_GEOM. Since GEOM will be the default for 5.0-RELEASE, it's advisable to run with GEOM now so you find the problems sooner rather than later. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message