|
From: Andreas <an...@po...> - 2002-02-18 23:11:58
|
Hello Michel Please excuse my late answer! >>> The Release file is signed, so if you worry about that, you can verify >>> the signature and then the package files with the MD5 sums in the >>> Release file. >> >> Hmm, but how to do that? > > The Release file GnuPG signature is in the Release.gpg file, or what do > you want to know? I dont know how to check that during base installation. >> But... I couldn't install on my second try tonight: Doing the base >> installation gave me a "malformed release file"! And I tried several times >> to connect to the server. What should that tell me? > > Use a basedebs tarball. ;) Wrong answer ;) > Seriously though, that's an infamous bug. I don't think it really has to > do with the Release file at all; at least when we installed a box at > work, the error seemed to appear to quickly for it to even have a chance > to download it. Is this with the 3.0.19 boot-floppies? Well, I used the stuff in current, of which I believed it would be a symlink to 3.0.19. Isn't it so? Well, as I checked the server with my webbrowser afterwards, it was very slow and not very nice to browse. Could it be that the server has been just too slow to serve the release file to the install system, so it gave up and produced a misleading error information? Or does the server simply not have the same priority on port 80 than on others under heavy load? BTW: Today I discovered to new kernel build, which you have obviously already done yesterday.. Thank you very much!! Hmm, but there is a minor problem: I can't unpack the kernel image lha archive, I only get errors. Some files seem to be ok, some not. Especially the vmlinuz file is not ok.. I've dowoloaded it two times to exclude connection errors, but the behaviour was still the same. -- All the best, Andi |