In <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> >From [EMAIL PROTECTED] Fri Aug 11 20:17:14 2000
> >Perhaps cdrecord could print a warning to that effect "warning: media size
> >exceeds writing capacity of this drive".
>
> One main decision for cdrecord is _not_ to have drive property tables
> compiled into cdrecord. .... Your wish needs to remain a wish ;-)
No drive property tables need be compiled in, only an option to specify
the name of the user defined drive properties table. Nothing which
changes should be compiled in, but the ability to read such a table at
run time could be.
I'm *not* saying I think this is a great idea, but if you should decide
to provide this I believe it should be in the same n,n,n notation used
elsewhere, not by drive vendor. If the drive does not return good id,
let the user be responsible for getting the limitations.
This is much the same way media capacity is done, isn't it? The
"remaining" value seems relative to the total available on the media. If
that approach is valid for media it seems valid for devices.
I shouldn't mind having cdrecord check by default the capacities
relative to the data to be written, and to require a "trust me" option
to continue (I would like that as a default) or have an option to stop
if the data will not fit.
Yes, obviously there are issues with cases where the length of the data
is not known, etc, my discussion is only of the case where cdrecord can
determine that data will not, or unlikely to, fit.
--
-bill davidsen ([EMAIL PROTECTED])
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
