Peter Jeremy wrote:
On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
burncd had some nice advantages over cdrecord: it came from the BSD
tree, it had capabilities for burning DVD+RW images. Disadvantage was
the limitation to ATA interface.
I see the latter as a disadvantage of
On Fri, Dec 29, 2006 at 12:15:37AM -0700, Scott Long wrote:
Did you know that ATAPI is actually just the SCSI command set that is
merely encapsulated into the IDE wire protocol?
This is something Linux has done (you can still use the direct ATA
and IDE subsystems if you want, but in most major
On Fri, 29 Dec 2006, Jeremy Chadwick wrote:
On Fri, Dec 29, 2006 at 12:15:37AM -0700, Scott Long wrote:
Did you know that ATAPI is actually just the SCSI command set that is
merely encapsulated into the IDE wire protocol?
This is something Linux has done (you can still use the direct ATA
and
On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
burncd had some nice advantages over cdrecord: it came from the BSD
tree, it had capabilities for burning DVD+RW images. Disadvantage was
the limitation to ATA interface.
I see the latter as a disadvantage of cdrecord: It only works on SCSI
On Fri, Dec 29, 2006 at 09:23:06AM +1100, Peter Jeremy wrote..
On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
burncd had some nice advantages over cdrecord: it came from the BSD
tree, it had capabilities for burning DVD+RW images. Disadvantage was
the limitation to ATA interface.
I
Hello!
On Tue, 26 Dec 2006, Luigi Rizzo wrote:
I suggest the following two fixes:
1. change burncd.c as below, so that if CDRIOCGETPROGRESS does not return
anything good, it calls CDIOCRESET to determine when the command
is complete.
This can be improved by calling CDIOCRESET
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x changes in two places:
* the ioctl handler, acd_get_progress() in /sys/dev/ata/atapi-cd.c
Luigi Rizzo [EMAIL PROTECTED] writes:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
[ .. stuff deleted .. ]
Patches below (to be
Luigi Rizzo wrote:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x changes in two places:
* the ioctl handler, acd_get_progress() in
On Wed, Dec 27, 2006 at 02:33:15AM +0100, Søren Schmidt wrote:
Luigi Rizzo wrote:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates, and i was able to write to
Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates, and
On Mon, Dec 25, 2006 at 05:12:04PM +0200, Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up
On Mon, Dec 25, 2006 at 04:55:54PM +0100, O. Hartmann wrote:
Since this is a very old and well known issue, and it seems there is no
one left solcing/developing this tool, it should be removed from the
source tree for the time it is to said broken.
burncd had some nice advantages over
Luigi Rizzo wrote:
On Mon, Dec 25, 2006 at 05:12:04PM +0200, Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever.
O. Hartmann wrote:
Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application
On Mon, Dec 25, 2006 at 12:00:41PM -0500, Scott Long wrote..
O. Hartmann wrote:
Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays
Hello!
On Mon, 25 Dec 2006, Scott Long wrote:
P.S.: Don't use burncd. Use cdrecord!
IMHO it isn't correct approach to avoid use of the tool _instead_ of
fixing
it. This way, all your tools will be broken one day ;)
Sincerely, Dmitry
Since this is a very old and well known issue, and it
Dmitry Pryanishnikov wrote:
1) it seems that problem is in /sys/dev/ata/atapi-cd.c code rather then
in burncd utility (but I'm not 100%-sure here);
2) burncd still does _all_ things which it's useful for: it really burns CDs
erases and fixates them. It just incorrectly waits for
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates, and i was able to write to
the disk a valid image, which probably means that the
disk
On Thu, Dec 21, 2006 at 09:27:17AM -0800, Luigi Rizzo wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates, and i was able to
21 matches
Mail list logo
