From owner-freebsd-current Sun Feb 20 12: 6:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id E04BE37BF9A for ; Sun, 20 Feb 2000 12:06:33 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id UAA09207; Sun, 20 Feb 2000 20:05:46 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id TAA18559; Sun, 20 Feb 2000 19:51:17 GMT (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <20000219171950.A81155@panzer.kdm.org> References: ; from rb@gid.co.uk on Sat, Feb 19, 2000 at 07:28:23PM +0000 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 20 Feb 2000 19:51:19 +0000 To: "Kenneth D. Merry" From: Bob Bishop Subject: Re: cdrecord problem with current current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 17:19 -0700 19/2/00, Kenneth D. Merry wrote: >On Sat, Feb 19, 2000 at 19:28:23 +0000, Bob Bishop wrote: >> Hi, >> >> cdrecord, freshly built on last night's -current: > >Freshly built? That's cdrecord 1.8a21, which is several versions old. I >think you should be using cdrecord 1.8 release from the ports tree. Uh, yes, it would have helped enormously if I'd actually installed it. Works just fine, sorry for the false alarm. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message