Tony Nelson wrote:
> > The effect of the readahead bug is to prevent the last few dozen KB
> > of the ISO from being read. I've done plenty of experiments.
> You are confused. The read is not prevented, it only returns less
> data than requested. Some badly written programs cannot deal with
>
On 10-03-03 15:52:23, Andre Robatino wrote:
> Tony Nelson wrote:
>
> > This is completely incorrect. The data on affected CDs and DVDs is
> > always longer than the data written. You should be able to figure
> > out for yourself why you must be wrong, and any experiments will
> > prove it to you
Tony Nelson wrote:
> This is completely incorrect. The data on affected CDs and DVDs is
> always longer than the data written. You should be able to figure
> out for yourself why you must be wrong, and any experiments will
> prove it to you. The "readahead bug" causes extra data to be
> returne
On 10-03-03 05:23:02, Andre Robatino wrote:
> Tony Nelson wrote:
>
> > Reading will never return more than the requested number of bytes.
> > It may read past the desired end of a CD or DVD. With that in
> > mind, read what I wrote above. If you don't understand it, ask a
> > question.
>
> I'm
On 03/02/2010 03:55 PM, John Mellor wrote:
> On Mon, 2010-03-01 at 21:53 -0500, Temlakos wrote:
>> I have downloaded this ISO twice, and verified it each time. I have made
>> no less than three "coasters" while trying to create a DVD from it. Then
>> I moved the ISO to another machine, and another
On Tue, 2 Mar 2010 23:31:08 -0800
Don Quixote de la Mancha wrote:
> The Chicken and Egg Problem for checksums was solved for the IP header
> checksum, and the TCP payload checksum back during the 1970s.
>
> When calculating the checksum, set the checksum field itself to zero.
> When verifying th
On Wednesday 03 March 2010, Mike McCarty wrote:
>Tim wrote:
>> On Tue, 2010-03-02 at 20:24 -0500, Andre Robatino wrote:
>>> I use the rawread script from
>>>
>>> http://www.troubleshooters.com/linux/coasterless.htm#rawread
>>>
>>> which automatically reads the correct size of the ISO, and runs a dd
Tony Nelson wrote:
> Reading will never return more than the requested number of bytes.
> It may read past the desired end of a CD or DVD. With that in mind,
> read what I wrote above. If you don't understand it, ask a question.
I'm not sure what you mean by "requested number of bytes", since y
On Wednesday 03 March 2010, Tim wrote:
>On Tue, 2010-03-02 at 20:24 -0500, Andre Robatino wrote:
>> I use the rawread script from
>>
>> http://www.troubleshooters.com/linux/coasterless.htm#rawread
>>
>> which automatically reads the correct size of the ISO, and runs a dd
>> command reading exactly
Don Quixote de la Mancha wrote:
> The Chicken and Egg Problem for checksums was solved for the IP header
> checksum, and the TCP payload checksum back during the 1970s.
That's Fletcher's checksum, which is not robust. It's possible to
put a 32 bit checksum into a program which it can use to check
The Chicken and Egg Problem for checksums was solved for the IP header
checksum, and the TCP payload checksum back during the 1970s.
When calculating the checksum, set the checksum field itself to zero.
When verifying the checksum, skip over the value that is actually
present. Perform the calcula
Tim wrote:
>
> It wasn't that chicken-and-egg situation that I was referring to, but
> the long standing issue that the self check has been bad for a very long
> time. If *something* *else* can manage to not read past the end of the
> disc, why can't it?
Ok, I misunderstood what you were referri
Andre Robatino:
>>> I use the rawread script from
>>>
>>> http://www.troubleshooters.com/linux/coasterless.htm#rawread
>>>
>>> which automatically reads the correct size of the ISO
Tim:
>> I have to ask: Why doesn't the installer's self test routine work that
>> way? This problem has been ar
On 10-03-02 20:24:03, Andre Robatino wrote:
> Tony Nelson wrote:
>
> > That test often fails due to a kernel issue, making good media seem
> > bad. I prefer to compare the bits with:
>
> > # cmp /dev/dvd /path/to/iso
>
> > If the dvd matches the iso: if there is no kernel issue there will
Tim wrote:
> On Tue, 2010-03-02 at 20:24 -0500, Andre Robatino wrote:
>> I use the rawread script from
>>
>> http://www.troubleshooters.com/linux/coasterless.htm#rawread
>>
>> which automatically reads the correct size of the ISO, and runs a dd
>> command reading exactly that much off the disc.
On Tue, 2010-03-02 at 20:24 -0500, Andre Robatino wrote:
> I use the rawread script from
>
> http://www.troubleshooters.com/linux/coasterless.htm#rawread
>
> which automatically reads the correct size of the ISO, and runs a dd
> command reading exactly that much off the disc.
I have to ask: W
Tony Nelson wrote:
> That test often fails due to a kernel issue, making good media seem
> bad. I prefer to compare the bits with:
> # cmp /dev/dvd /path/to/iso
> If the dvd matches the iso: if there is no kernel issue there will
> be no output; else it will complain about eof on the iso f
On Tue, Mar 2, 2010 at 3:55 PM, John Mellor wrote:
> I think its all part of the insufficient testing problem that has dogged
> F12 ever since it was released without being stabilized. Hopefully the
> revised F13 qa automation and fixing of blocker anaconda bugs so that
> testers can actually ins
On Mon, 2010-03-01 at 21:53 -0500, Temlakos wrote:
> I have downloaded this ISO twice, and verified it each time. I have made
> no less than three "coasters" while trying to create a DVD from it. Then
> I moved the ISO to another machine, and another program--which then
> proceeded to tell me th
On Tuesday 02 March 2010, Mike McCarty wrote:
>
> I have used K3b for several years, and never had a problem with it.
> If you prefer the GUI way, then I recommend it. It's a front end
> to cdrecord.
>
[snip]
> I don't like KDE, but the GNOME tools for CDs and DVDs I've
> had problems with. Neve
On 10-03-02 11:26:09, Don Quixote de la Mancha wrote:
> Good for you!
>
> When you first boot the install CD, it presents the option of
> validating the DVD contents, to ensure that you really do have a good
> burn. Let it do that check at least once. If the test every
> succeeds, it will probab
Temlakos wrote:
> Happily, I substituted "cdrecord" for "wodim" in that command line.
> Forty minutes later, I now have a disk that I have every reason to
> suppose will work as intended. The burn surface looks as though it
> accepted a burn of about 3 GB, and cdrecord returned only one warning
Good for you!
When you first boot the install CD, it presents the option of
validating the DVD contents, to ensure that you really do have a good
burn. Let it do that check at least once. If the test every
succeeds, it will probably always succeed, but you sure don't want to
try to install from
Don Quixote de la Mancha wrote:
> On Tue, Mar 2, 2010 at 6:36 AM, Temlakos wrote:
>
>> Sadly, I don't seem to have wodim on my system. (I never upgraded beyond
>> FC6, if that explains anything.) How do I get it?
>>
>
> FC6 would have cdrecord. I think wodim and cdrecord have compatible
>
On Tue, Mar 2, 2010 at 6:36 AM, Temlakos wrote:
> Sadly, I don't seem to have wodim on my system. (I never upgraded beyond
> FC6, if that explains anything.) How do I get it?
FC6 would have cdrecord. I think wodim and cdrecord have compatible
command-line options. If I remember correctly, there
Don Quixote de la Mancha wrote:
> Try burning it with wodim. It's a command-line tool; you'll need to
> read wodim's man page, which will require a bit of study.
>
> One reason is that wodim is likely to succeed where other burners
> fail. The other is that wodim will give extremely detailed erro
Try burning it with wodim. It's a command-line tool; you'll need to
read wodim's man page, which will require a bit of study.
One reason is that wodim is likely to succeed where other burners
fail. The other is that wodim will give extremely detailed error
messages if something goes wrong.
I do
if you can, go ahead and tell ys the exact steps you used, from start
to finish. tell us what you downloaded, where you copied it, what you
did, what app you used, what you typed in, etc.. give us each step..
someone wil point out the err in no time!
peace
On Mon, Mar 1, 2010 at 8:21 PM, Patric
Patrick O'Callaghan wrote:
> On Mon, 2010-03-01 at 21:53 -0500, Temlakos wrote:
>
>> I have downloaded this ISO twice, and verified it each time. I have made
>> no less than three "coasters" while trying to create a DVD from it. Then
>> I moved the ISO to another machine, and another program--
On Mon, Mar 1, 2010 at 7:31 PM, Mike McCarty wrote:
> This sounds like you have a hardware problem, or are not using
> the correct procedure to do the burn.
Try burning the DVD at a lower speed. If you are using wodim, use
"speed=1" on the command line.
Try buying a completely different brand o
On Mon, 2010-03-01 at 21:53 -0500, Temlakos wrote:
> I have downloaded this ISO twice, and verified it each time. I have made
> no less than three "coasters" while trying to create a DVD from it. Then
> I moved the ISO to another machine, and another program--which then
> proceeded to tell me th
Temlakos wrote:
> I have downloaded this ISO twice, and verified it each time. I have made
> no less than three "coasters" while trying to create a DVD from it. Then
> I moved the ISO to another machine, and another program--which then
> proceeded to tell me that the ISO looked like a CD, not a
Temlakos wrote:
> I have downloaded this ISO twice, and verified it each time. I have made
> no less than three "coasters" while trying to create a DVD from it. Then
> I moved the ISO to another machine, and another program--which then
> proceeded to tell me that the ISO looked like a CD, not a
I have downloaded this ISO twice, and verified it each time. I have made
no less than three "coasters" while trying to create a DVD from it. Then
I moved the ISO to another machine, and another program--which then
proceeded to tell me that the ISO looked like a CD, not a DVD.
What's going on? H
34 matches
Mail list logo
