Re: cdrecord and large files.



Joerg Schilling wrote:

As a result cdrecord would not even work if run by root.

I am not sure which variant would give me more confused users.....


I cant answer that. I know I found it very confusing when the program got permission denied when started by root.

I think it would be sensible to print a explanation where permission is denied, when one might reasonably expect permission to be granted. It is quite reasonable for root to expect to be able to read a file. The fact root cant, needs some explanation. Simply putting "permission denied" is not really sufficient in a case like this.

A slightly more informative error message should not confuse anyone and might save a lot of headache. Normally if one gets "permission denied" when using a UNIX system, it will not take any half-sensible person to work out why the permission is denied. But in this case the reasons are far from obvious, so need a bit of explanation.
.



Relevant Pages

  • Re: paint balling
    ... the reasons that all of you think ... for an explanation of why it was banned so that he could explain it to ... But the OP claims that they only 'think' they cant do the activity, ... OP was aware of the specific rule, so why phrase it as if there was. ...
    (uk.rec.scouting)
  • Re: Dont Forget Mises -- and Dump the Third Way!
    ... > clear explanation of why returns to capital exist is ... nothing confused or confusing about explanation that ... I would simply note that I never claimed I was explaining ... you regarding preferences ...
    (sci.econ)
  • Re: [PHP] PHP textbook suggestions?
    ... As to why I think one style is good or bad-- probably the same reasons ... So they naturally want to know-- why the double quotes? ... that DOES need double quotes-- so it is very confusing to them. ... totally inconsistent. ...
    (php.general)
  • Re: Can I write Silverlight applications in VB?
    ... Thanks for the explanation. ... These product names really are confusing. ... Well I'm not sure what I need, I'm stuck to Visual Basic 1. ...
    (microsoft.public.vb.general.discussion)