From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ]
Date: Mon, 30 Jan 2006 19:01:51 -0600 [thread overview]
Message-ID: <43DEB6FF.1020505@shaw.ca> (raw)
In-Reply-To: <5AKRr-4V5-19@gated-at.bofh.it>
Joerg Schilling wrote:
> There is no such bug in libscg.
>
> There is nothing that has been freezed.
>
> If you have the apropriate privs to send SCSI commands to any SCSI device
> on the system, you will not come across your problem.
>
> Now let us try to talk about real problems or stop this discussion.
It appears that you are wanting to blame all of these problems on Linux
and refuse to accept the possibility that cdrecord/libscg is doing
things incorrectly from a Linux perspective. If you want to "talk about
real problems" you must accept this possibility.
Why should I have to give privileges to send SCSI commands to any device
in the system just to write CDs? The answer, it would appear, is that
cdrecord is messing with things (i.e. /dev/sg interface) it has no
business messing with in current Linux systems, since that interface
should not be necessary for the purpose of cdrecord.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-01-31 1:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5zENZ-72l-47@gated-at.bofh.it>
[not found] ` <5AiBB-5AH-17@gated-at.bofh.it>
[not found] ` <5AiV2-62l-7@gated-at.bofh.it>
[not found] ` <5AJ9s-2go-23@gated-at.bofh.it>
[not found] ` <5AKHI-4IV-5@gated-at.bofh.it>
[not found] ` <5AKRr-4V5-19@gated-at.bofh.it>
2006-01-31 1:01 ` Robert Hancock [this message]
2006-01-27 16:37 CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ] Bartlomiej Zolnierkiewicz
2006-01-29 11:01 ` Joerg Schilling
2006-01-29 11:15 ` Jan Engelhardt
2006-01-29 11:28 ` Matthias Andree
2006-01-30 15:24 ` Joerg Schilling
2006-02-05 12:03 ` Jan Engelhardt
2006-02-06 16:29 ` Joerg Schilling
2006-02-06 17:17 ` René Rebe
2006-02-06 18:02 ` Matthias Andree
2006-01-29 11:26 ` Matthias Andree
2006-01-29 20:41 ` Jan Engelhardt
2006-01-29 20:50 ` Joerg Schilling
2006-01-29 21:28 ` Albert Cahalan
2006-01-30 16:11 ` Joerg Schilling
2006-01-30 16:31 ` Albert Cahalan
2006-01-30 16:35 ` Joerg Schilling
2006-01-30 17:08 ` Matthias Andree
2006-01-30 17:14 ` Joerg Schilling
2006-01-30 17:30 ` Matthias Andree
2006-01-30 17:37 ` Joerg Schilling
2006-01-30 17:49 ` Matthias Andree
2006-01-30 20:22 ` James Courtier-Dutton
2006-01-31 10:17 ` Andreas Jellinghaus
2006-01-30 20:24 ` Phillip Susi
2006-01-31 10:47 ` Joerg Schilling
2006-01-31 11:22 ` Matthias Andree
2006-02-01 0:15 ` Bill Davidsen
2006-02-01 7:45 ` Tejun Heo
2006-02-01 16:41 ` Joerg Schilling
2006-01-31 23:55 ` Bill Davidsen
2006-02-01 15:06 ` Joerg Schilling
2006-01-30 15:25 ` Joerg Schilling
2006-01-30 17:09 ` Matthias Andree
2006-01-30 17:15 ` Joerg Schilling
2006-01-30 23:26 ` Pavel Machek
2006-02-01 15:51 ` Jan Engelhardt
2006-01-31 1:43 ` Patrick McFarland
[not found] ` <515e525f0601302205h4a845f36u12b946515759239a@mail.gmail.com>
2006-01-31 6:46 ` Kyle Moffett
2006-01-31 8:55 ` Pekka Enberg
2006-02-01 0:25 ` Jesper Juhl
2006-02-02 16:45 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43DEB6FF.1020505@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox