Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices

[Matthias Andree]

On Mon, 09 Aug 2004, Albert Cahalan wrote:

> Shall we rip the printk() calls out of the kernel? Many
> of them are weird. They might confuse the end users.
> 
> Joerg:
>    "WARNING: Cannot do mlockall(2).\n"
>    "WARNING: This causes a high risk for buffer underruns.\n"
> Fixed:
>    "Warning: You don't have permission to lock memory.\n"
>    "         If the computer is not idle, the CD may be ruined.\n"
> 
> Joerg:
>    "WARNING: Cannot set priority class parameters priocntl(PC_SETPARMS)\n"
>    "WARNING: This causes a high risk for buffer underruns.\n"
> Fixed:
>    "Warning: You don't have permission to hog the CPU.\n"

"hog" certainly is not the right word here, but let's not discuss
application warnings on word level here.

>    "         If the computer is not idle, the CD may be ruined.\n"

The warning still needs to contain a technical information that the end
user can report to the support or maintainer. Jörg's warning isn't all
too bad only the user may not know what a buffer underrun actually
means, so another line of explanation, a recommendation to retry with
increased (root) privileges and preferably another 10 s delay would iron
this out.

Note that while the burn-proof/just-link feature allows the drive to
pick up writing but it comes at a price, a few dozen pits/lands are
hosed for every time this feature gets used, so it's best to avoid
interrupting the write stream.

One of Jörg's goals appears to let his application do the best possible
job without such micro gaps, and that deserves all support he can get.

That the DMA, ide-scsi, interfaces and naming issues can't be settled is
sad and it appears as though the naming and it seems these issues cannot
be discussed separately for some reason.

-- 
Matthias Andree

NOTE YOU WILL NOT RECEIVE MY MAIL IF YOU'RE USING SPF!
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/