From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 01:58:16 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id BB69D106566C; Tue, 27 Sep 2011 01:58:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 0957315607C; Tue, 27 Sep 2011 01:58:15 +0000 (UTC) Message-ID: <4E812DB7.3000302@FreeBSD.org> Date: Mon, 26 Sep 2011 18:58:15 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.2) Gecko/20110912 Thunderbird/6.0.2 MIME-Version: 1.0 To: Craig Rodrigues References: <201109262324.p8QNO0NN070853@freefall.freebsd.org> <4E811FF7.7010607@a1poweruser.com> <4E8126D3.5020407@FreeBSD.org> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Fbsd8 , eadler@freebsd.org, FreeBSD Questions , freebsd-current@freebsd.org Subject: Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 27 Sep 2011 01:58:16 -0000 On 09/26/2011 18:43, Craig Rodrigues wrote: > On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton wrote: >>> burncd has been part of the system utilities included in the basic >>> release since release 4.0 and cdrecord is a port. The professional >>> solution is to remove burncd from the 9.0 system release and add the >>> cdrecord command to the basic release as the replacement for burncd. >>> Then add release notes entry of the change. >> >> I think you misunderstand the situation. So here are a few hopefully >> helpful facts: >> >> 1. The fact that something is in the base, or in the ports, has >> absolutely no bearing on whether one piece of software is fundamentally >> more useful or valuable than another. > > > Hi, > > I have used burncd on many releases of FreeBSD, on many machines > without problem. I can see the fact that burncd suddenly failing to > work on ATAPI hardware could annoy and confused end-users. It doesn't fail to work on ATAPI hardware. It fails to work on cd0 which is a SCSI device. The fact that it's emulated doesn't matter. > Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out > a more useful error message? Sure, as soon as someone volunteers to create that patch. No one is *trying* to annoy users, but things change around here because people are interested in changing them. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/