Adam Di Carlo <[EMAIL PROTECTED]> wrote on 12 May 2001 13:18:04 -0400: > I cannot reproduce this. Nor can any of my friends. We have done > many network installs. > Closing this bug, it's very wrong. I disagree. I have replicated this on my system, and it is a major pain. Using 2.2.19pre17 rescue floppy from 'testing': dan$ md5sum testing-rescue.144.bin 3745f3d17b0f9ad30a2859661224d815 testing-rescue.bin with the companion root floppy: dan$ md5sum testing-root.144.bin b0713b08ae5f772ef926dea0a7121d41 testing-root.bin (sorry, they're my file names not whatever is on the download site.) lilo_1%3a21.7.1-4_i386.deb exists as it should in /var/cache/apt/archives after the base system install. The file appears to be valid (I unpacked it with ar, tar and gzip.) I am pretty sure the problem is simply that lilo isn't being installed. Let me know if there is any other info I can give you to help solve this annoying problem. -- Dan Shearer Open Source Manager Mob: +61 411 49 1800 Tel: +61 8 8130 3104 [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
