From owner-freebsd-current@FreeBSD.ORG Wed Jun 4 13:11:10 2003 Return-Path: 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 DFFFF37B401 for ; Wed, 4 Jun 2003 13:11:10 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2C3E43F75 for ; Wed, 4 Jun 2003 13:11:09 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h54KB8nA037463 for ; Wed, 4 Jun 2003 22:11:08 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Wed, 04 Jun 2003 22:11:08 +0200 Message-ID: <37462.1054757468@critter.freebsd.dk> Subject: HEADSUP: ccd migration issue for some. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 20:11:11 -0000 In a few days time I will flip the switch so that we run on the new GEOMified CCD. In all my tests, the new CCD is compatible with the old CCD, but it does require an updated ccdconfig(8) program. This is nothing out of the ordinary, unless you happen to have your /usr/src or /usr/obj stored on a ccd volume, in which case you would do well in squirilling away a copy of the old ccdconfig(8) binary along with your fall back kernel. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.