Joerg Schilling wrote:
From: Samuel Tardieu [EMAIL PROTECTED]
The manpage of cdrecord says:
The default is to turn BURN-Free off, regardless of the
defaults of the drive.
What is the rationale for doing that? Shouldn't burn-free be turned on
by default, or at
Joerg Schilling wrote:
From: Samuel Tardieu [EMAIL PROTECTED]
The manpage of cdrecord says:
The default is to turn BURN-Free off, regardless of the
defaults of the drive.
What is the rationale for doing that? Shouldn't burn-free be turned on
by default, or at
From: Samuel Tardieu [EMAIL PROTECTED]
The manpage of cdrecord says:
The default is to turn BURN-Free off, regardless of the
defaults of the drive.
What is the rationale for doing that? Shouldn't burn-free be turned on
by default, or at least be let untouched by cdrecord to
The manpage of cdrecord says:
The default is to turn BURN-Free off, regardless of the
defaults of the drive.
What is the rationale for doing that? Shouldn't burn-free be turned on
by default, or at least be let untouched by cdrecord to preserve the writer's
default behaviour?
On Wed, Nov 19, 2003 at 08:35:12PM +0100, Samuel Tardieu wrote:
The manpage of cdrecord says:
The default is to turn BURN-Free off, regardless of the
defaults of the drive.
What is the rationale for doing that? Shouldn't burn-free be turned on
by default, or at least be
The manpage of cdrecord says:
The default is to turn BURN-Free off, regardless of the
defaults of the drive.
What is the rationale for doing that? Shouldn't burn-free be turned on
by default, or at least be let untouched by cdrecord to preserve the writer's
default behaviour?
On Wed, Nov 19, 2003 at 08:35:12PM +0100, Samuel Tardieu wrote:
The manpage of cdrecord says:
The default is to turn BURN-Free off, regardless of the
defaults of the drive.
What is the rationale for doing that? Shouldn't burn-free be turned on
by default, or at least be
7 matches
Mail list logo
