From owner-freebsd-questions@FreeBSD.ORG Tue Sep 27 02:11:03 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67E1C1065674; Tue, 27 Sep 2011 02:11:03 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id C56CA8FC21; Tue, 27 Sep 2011 02:11:02 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so7802833bkb.13 for ; Mon, 26 Sep 2011 19:11:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PBbgpofa18q3GpCtgfQIUTPVO2rW1mr75JVh6BjFqjI=; b=Fee2ulbTLZ2RPdqsn8mwSFWkFovT2VxvjMwEotE+GU7nbIJlx8/3wTythKKGmwsQuX 3d09XgLDgHsxLrLB8yJYibaSg2XJwSGNqJylrXxe9ihqiPXt53TIHrF4sGC+pwDH2aX/ GT4s+dUidmTOT07PY89XLFBd6hx4HcSFJ9rB0= MIME-Version: 1.0 Received: by 10.204.154.136 with SMTP id o8mr4325777bkw.355.1317087784851; Mon, 26 Sep 2011 18:43:04 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.204.140.24 with HTTP; Mon, 26 Sep 2011 18:43:04 -0700 (PDT) In-Reply-To: <4E8126D3.5020407@FreeBSD.org> References: <201109262324.p8QNO0NN070853@freefall.freebsd.org> <4E811FF7.7010607@a1poweruser.com> <4E8126D3.5020407@FreeBSD.org> Date: Mon, 26 Sep 2011 18:43:04 -0700 X-Google-Sender-Auth: Im1m0qB0-4YYnSaEOJQp_mmkUJU Message-ID: From: Craig Rodrigues To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 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-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2011 02:11:03 -0000 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. Fbsd8 has a valid point. Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out a more useful error message? "ERROR: burncd does not work when ATAPI-CAM driver enabled. Install the sysutils/cdrtools port and use cdrecord instead. Please refer to http://www.freebsd.org/doc/handbook/creating-cds.html#CDRECORD" While it is necessary to document all these things in release notes, documentation, etc., I don't always read every single last line of documentation or release notes when using a system, and I suspect many end-users are the same. :) I am a big fan of having the system issue diagnostic errors that give the user a clue how to remedy the problem, or pointers to relevant information. I even put "Please" in the error message to be nice. :) -- Craig Rodrigues rodrigc@crodrigues.org