From owner-freebsd-current@FreeBSD.ORG Tue Aug 31 12:16:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9889016A4CF; Tue, 31 Aug 2004 12:16:40 +0000 (GMT) Received: from web.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBDE943D4C; Tue, 31 Aug 2004 12:16:39 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.20] (portacare.portaone.com [195.140.247.242]) (authenticated bits=0) by web.portaone.com (8.12.8p2/8.12.8) with ESMTP id i7VCGXPR073504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Aug 2004 14:16:35 +0200 (CEST) (envelope-from sobomax@portaone.com) Message-ID: <41346C0F.5010109@portaone.com> Date: Tue, 31 Aug 2004 15:16:15 +0300 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= References: <4133683A.3090201@portaone.com> <4134530C.6020309@portaone.com> <413465C4.9020800@DeepCore.dk> In-Reply-To: <413465C4.9020800@DeepCore.dk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit cc: =?UTF-8?B?RGFnLUVybGluZyBTbdCscmdyYXY=?= cc: current@FreeBSD.ORG cc: sos@FreeBSD.ORG Subject: Re: burncd(8) usability: why `-s max' isn't default? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 31 Aug 2004 12:16:40 -0000 Søren Schmidt wrote: > Maxim Sobolev wrote: > >> Dag-Erling Smørgrav wrote: >> >>> Maxim Sobolev writes: >>> >>>> I wonder if there are any compelling reasons why `-s max' is not >>>> default behaviour of burncd(8). IMHO, there is no point to have >>>> default of 4. Usually, today's drives are smart enough to select the >>>> maximum speed supported both by drive and by the medium. >>> >>> >>> Plenty of drives aren't, especially with cheap media. >> >> >> Do you have any evidence? >> >> I know what I am talking about. We are working on the mass-product >> based on FreeBSD. This product will have to burn data CDs. We have >> tried compatibility of various media with `-s max', including very >> cheap ones and have never seen any corruption due to speed mismatch. >> Virtually all media available on the market today has a special track, >> which records its speed rating and manufacturer. > > > If you know what you are talking about, and is in the process of making a > FreeBSD product, I'm sure you also know how to patch FreeBSD to do what > you want for that product. Yes, I know how to do it, but it is not the topic of this discussion. Apart from my commercial activity, I am running quite large FreeBSD user group in my country, so that improving OOB FreeBSD useability concerns me. > For the "free" version of FreeBSD I'd prefer we stick to what we have, > there > are way too many crappy burners/media out there that will produce bad > results, > and that translates into mails in my inbox with complaints that I can > easily > live without.... Few of my friends were quite surprised when I've told them about '-s max' option and how useful it is. I wonder how many FreeBSD users out there don't know about it as well and wonder why FreeBSD is so slow when burning at their brand-new zillon-speed CD-RW drive. BTW, maybe it would be better to add logic to read media's max speed into burncd/atapicd and throttle burning accordingly? For example with cdrdao(8) it is possible to do something like the following using atapicam: -bash-2.05b$ sudo cdrdao disk-info -v 0 --device 1,0,0 --driver generic-mmc | grep ^Reco Recording Speed : 0X - 8X -bash-2.05b$ We've confirmed that it produces accurate results for all types and speeds we've been able to find on market. -Maxim