I may have made a mistake in using driveropts=burnfree while doing a burn
of the slint iso using cdrskin I don't know for sure one way or the other.
I suspect it's possible since more sectors got written than got read from
the iso.
This time I got me a slint.log file I hope with all of the corrupted
packages stored in that log.
How I did that on the slint disk was first to have a flash disk in the
machine with a formatted partition and that was mounted to /mnt on the
machine.
When I ran start on slint installer I ran it like:
start 2>&1 | tee /mnt/slint.log
I put that information here so if anyone else runs into errors after
having verified the slint64-15.0-5.iso.asc with slint64-15.0-5.iso with
Didier's key imported and using GPG-KEY and the output was good signature
that came up twice you'll know how to capture install errors.
-- Jude <jdashiel at panix dot com> "There are four boxes to be used in
defense of liberty: soap, ballot, jury, and ammo. Please use in that
order." Ed Howdershelt 1940.
===============================================================================
The Slint mailing list.
Archive: https://www.freelists.org/archive/slint
To subscribe or unsubscribe, email slint-request@xxxxxxxxxxxxx with the subject
'subscribe' or 'unsubscribe', then answer the email you will receive.
More: email slint-request@xxxxxxxxxxxxx with as subject 'help' or 'commands'.
