From: Michel <mi...@da...> - 2002-02-19 00:50:39
|
On Die, 2002-02-19 at 00:08, Andreas W=FCst wrote: >=20 > >>> The Release file is signed, so if you worry about that, you can verif= y > >>> the signature and then the package files with the MD5 sums in the > >>> Release file. > >>=20 > >> Hmm, but how to do that? > >=20 > > The Release file GnuPG signature is in the Release.gpg file, or what do > > you want to know? >=20 > I dont know how to check that during base installation. The boot-floppies don't provide the means yet. If you really care about security so much, making your own mirror and verifying it isn't asking too much IMHO. It boils down to whether you trust the key the signature was made with anyhow. > > Seriously though, that's an infamous bug. I don't think it really has t= o > > 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 chanc= e > > to download it. Is this with the 3.0.19 boot-floppies? >=20 > Well, I used the stuff in current, of which I believed it would be a syml= ink > to 3.0.19. Isn't it so? Yes, I'd just hoped this bug had been fixed. No such luck obviously. > 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 to= o > slow to serve the release file to the install system, so it gave up and > produced a misleading error information? I doubt it; at work, the error appeared instantly, which led us to believe that the problem isn't really with the file but the network. Looking at http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=3Dno&bug=3D132838, tha= t seems to be the case indeed. > Or does the server simply not have the same priority on port 80 than on > others under heavy load? Port 80 is http. ;) > BTW: Today I discovered to new kernel build, which you have obviously alr= eady > 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.. >=20 > I've dowoloaded it two times to exclude connection errors, but the behavi= our > was still the same. Get a new lha. ;) The latest one in Debian sports lh7 compression. Anyway, I've uploaded a new archive with lh6 max. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |