On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton <do...@freebsd.org> 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 rodr...@crodrigues.org _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"