Wim De Smet wrote:
It was LG. The model was an IDE cdrom drive that wasn't supposed to
implement the command in question. I think it was the flush command
which is apparently only used by cd-r(w) drives. The drive implemented
this as "flush firmware".
pretty funny story if you think of it. :-)
N
On Tue, 24 Aug 2004 15:31:31 +0800, John Summerfield
<[EMAIL PROTECTED]> wrote:
> Brian Pack wrote:
>
> >With the old
> >kernel, a user could potentially wipe a drives firmware.
> >
> >
> >
> which actually happend with a release of Mandrake Linux and some brand I
> won't name coz I don't recall i
Brian Pack wrote:
With the old
kernel, a user could potentially wipe a drives firmware.
which actually happend with a release of Mandrake Linux and some brand I
won't name coz I don't recall its name of CD-ROM.
The manufactorer misused one of the standard SCSI commands:-)
--
Cheers
John
-- sp
On Tue, Aug 24, 2004 at 08:53:12AM +0800, csj wrote:
> Pretty well-known issues;-) 2.6.8.x breaks current versions of at
> least two of the most popular optical media writing tools,
> cdrecord and growisofs.
I knew there was a reason I stayed with the 2.6.5 kernel I was running. :)
--
Marc Wils
Hello
Marc Wilson (<[EMAIL PROTECTED]>) wrote:
> On Mon, Aug 23, 2004 at 04:44:15PM -0400, Brian Pack wrote:
>> I've been hit with the issues between cdrecord and the 2.6.8 kernel.
>
> "The" issues... what issues?
Kernel 2.8 has an "improved" security model that (for now) does not
allow normal
* Brian Pack <[EMAIL PROTECTED]> [2004:08:23:16:44:15-0400] scribed:
> I've been hit with the issues between cdrecord and the 2.6.8 kernel.
Does this also affect cdrdao?
My boxen are at 2.6.3x, and I have considered upping them . . .
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fi
On 23. August 2004 at 3:06PM -0700,
Marc Wilson <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 23, 2004 at 04:44:15PM -0400, Brian Pack wrote:
> > I've been hit with the issues between cdrecord and the 2.6.8
> > kernel.
>
> "The" issues... what issues?
Pretty well-known issues;-) 2.6.8.x breaks curre
On Tue, 2004-08-24 at 10:36, Brian Pack wrote:
> Haven't you heard? IIRC the kernel 2.6.8 plugged a security hole that
> cdrecord used to function. Once the hole was closed, users could no
> longer run cdrecord as they could in previous kernels. With the old
> kernel, a user could potentially wipe
On Mon, 2004-08-23 at 18:06, Marc Wilson wrote:
> On Mon, Aug 23, 2004 at 04:44:15PM -0400, Brian Pack wrote:
> > I've been hit with the issues between cdrecord and the 2.6.8 kernel.
>
> "The" issues... what issues?
Haven't you heard? IIRC the kernel 2.6.8 plugged a security hole that
cdrecord us
On Mon, Aug 23, 2004 at 04:44:15PM -0400, Brian Pack wrote:
> I've been hit with the issues between cdrecord and the 2.6.8 kernel.
"The" issues... what issues?
--
Marc Wilson | The Phone Booth Rule: A lone dime always gets the
[EMAIL PROTECTED] | number nearly right.
signature.asc
De
s expected.
For now, I've reverted to kernel 2.6.7, where my audio cds burn fine.
I could stay with 2.6.7. I could patch my kernel, but my confidence in
my kernel patching skills are low to nonexistent. I'm wondering if there
is an alternative to cdrecord that works with kernel 2.6.8 as
11 matches
Mail list logo