From owner-freebsd-bugs@FreeBSD.ORG Sun Sep 25 13:10:07 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2169B1065672 for ; Sun, 25 Sep 2011 13:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0C0CB8FC15 for ; Sun, 25 Sep 2011 13:10:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p8PDA6JZ035761 for ; Sun, 25 Sep 2011 13:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p8PDA6M6035760; Sun, 25 Sep 2011 13:10:06 GMT (envelope-from gnats) Date: Sun, 25 Sep 2011 13:10:06 GMT Message-Id: <201109251310.p8PDA6M6035760@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Fbsd8 Cc: Subject: Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fbsd8 List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Sep 2011 13:10:07 -0000 The following reply was made to PR bin/160979; it has been noted by GNATS. From: Fbsd8 To: Jaakko Heinonen Cc: bug-followup@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0 Date: Sun, 25 Sep 2011 08:44:48 -0400 Jaakko Heinonen wrote: > On 2011-09-24, Joe Barbish wrote: >> It seems that in 9.0 the cd/dvd/drive is now given a dev name of cd0 >> where in all previous releases it was acd0. >> Tried to use the system burncd command in 9.0 and got this error msg >> >> burncd: ioctl(CDRIOCGETBLOCKSIZE): Inappropriate ioctl for device >> >> Tested using "burncd -f acd0" and "burncd -f cd0". >> In both cases got the same error message. >> >> Looks to me like the burncd command needs to be fixed >> to work in 9.0. > > burncd(8) supports only acd(4) driver. In 9.0 the default is the new > CAM-based ATA stack which uses cd(4) (UPDATING entry 20110424). > > It's unlikely that a support for cd(4) will be added to burncd(8). > > I think this should be mentioned in release notes. > Fixing burncd should be a priority, this PR gets it into the "must fix queue" before the next round of beta or RC releases. Yes you have identified what is causing it to not work, but you have not followed through. The next step is to assign it to someone to work on it now. Thats the whole idea of the PR system and beta testing. If burncd is not going to work in 9.0 then it should be removed from the release all together. Has any research been done to identify other system commands or ports that changing the system default from acd0 to cd0 effects?