From owner-freebsd-current Tue Sep 8 10:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05967 for freebsd-current-outgoing; Tue, 8 Sep 1998 10:10:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05961 for ; Tue, 8 Sep 1998 10:10:11 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id KAA13938; Tue, 8 Sep 1998 10:08:50 -0700 (PDT) Date: Tue, 8 Sep 1998 10:08:49 -0700 (PDT) From: Ian Kallen Reply-To: Ian Kallen To: John Birrell cc: freebsd-current@FreeBSD.ORG Subject: Re: CAM & current In-Reply-To: <199809050128.LAA13608@cimlogic.com.au> 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 Since I'm trying to use CAM in 3.0, I don't see why I shouldn't raise attention to show stopping errors. Everything is supposed to magically start working without user input on September 15? I'm looking forward to CAM's the mainstream integration on the 13th. On Sat, 5 Sep 1998, John Birrell wrote: :Or perhaps you just let Justin concentrate on getting CAM ready for 3.0. :There will be time for people to play with goodies in 3.0 after Sept 15. -- Ian Kallen ICQ: 17073910 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message