From: Ville Herva [EMAIL PROTECTED]
When (accidentally) trying to burn ~670MB onto a 74 cdr disk, I experienced
a complete lock up.
It went to 99% (as one would expect), and then drive began giving weird
sounds -
From [EMAIL PROTECTED] Sun Oct 21 13:46:25 2001
On Sun, Oct 21, 2001 at 01:37:01PM +0200, you [Joerg Schilling] claimed:
Thanks for the timely reply!
This must be a broken drive
Hmm. It used to work with 2.2-kernel. With too large image, it just gave an
error.
I may only judge from
On Sun, Oct 21, 2001 at 01:56:06PM +0200, you [Joerg Schilling] claimed:
Hmm. It used to work with 2.2-kernel. With too large image, it just gave an
error.
I may only judge from information you provide, not from information you hide.
I did say that in the original report:
It used to give
From [EMAIL PROTECTED] Sun Oct 21 14:08:12 2001
On Sun, Oct 21, 2001 at 01:56:06PM +0200, you [Joerg Schilling] claimed:
Hmm. It used to work with 2.2-kernel. With too large image, it just gave an
error.
I may only judge from information you provide, not from information you hide.
I did
So sprach »Joerg Schilling« am 2001-10-19 um 12:41:11 +0200 :
A typical Linux user buys a SuSE distribution more than once a year.
A typical Solaris user loads the CD binaries over the internet.
You cannot load the SuSE CD's over the internet.
Well, a typical Linux user uses Mandrake and
On Sun, Oct 21, 2001 at 02:10:18PM +0200, you [Joerg Schilling] claimed:
Ok. I'll compile the newest from source.
But do you think the too-large-image lock up might be cured with a newer
cdrecord, or should is the kernel the prime suspect?
It least recent libscg versions include a
6 matches
Mail list logo
