Date: Mon, 26 Sep 2011 20:59:35 -0400 From: Fbsd8 <fbsd8@a1poweruser.com> To: eadler@FreeBSD.org, FreeBSD Questions <freebsd-questions@FreeBSD.org>, freebsd-current@freebsd.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0 Message-ID: <4E811FF7.7010607@a1poweruser.com> In-Reply-To: <201109262324.p8QNO0NN070853@freefall.freebsd.org> References: <201109262324.p8QNO0NN070853@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
eadler@FreeBSD.org wrote: > Synopsis: 9.0 burncd error caused by change to cd0 from acd0 > > State-Changed-From-To: open->analyzed > State-Changed-By: eadler > State-Changed-When: Mon Sep 26 23:24:00 UTC 2011 > State-Changed-Why: > requires only a release notes entry; use cdrecord instead of burncd > > http://www.freebsd.org/cgi/query-pr.cgi?pr=160979 > > Your solution is very un-professional. What your solution purposes to do is do nothing. I think your judgment is flawed and a larger group of your peers need to review your judgment in this case. 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. You do not knowingly leave a non-working utility in the system, period, or not provide a included replacement for a popular utility as this one. The alternative is to fix burncd or backout the acd0 to cd0 change from 9.0 which may be the most desired solution because its obvious that no one researched the impact this change may have. This change may impact many ports that access cd/dvd drives for read and write access. burncd may be a very small worm in a large can of big worms.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E811FF7.7010607>