Frans Pop wrote: > On Sunday 11 July 2004 22:34, Joey Hess wrote: > > The 2.6 kernel recently changed to use 2.6.7. The kernel udebs for that > > kernel are only present in unstable. If you tell d-i to install testing, > > then it will also take udebs from testing, which means it will find no > > kernel modules to load. This is usual; if you want to test netboot > > installs of sid's d-i, you must tell it to install sid. Note that you > > can go back and change it to install sarge after it has downloaded the > > udebs. > > Right. With that information I now have a successful 2.6.7 install on my > laptop (with the libpth2 workaround) :-) > > How about adding a test for this situation in net-retriever (where it > currently says "# TODO: Verify the integrity")? > > Something like (replacing the 5 lines after the TODO): > KVER=`uname -r` > [ "$ext" = .gz ] && CAT="zcat" || CAT="cat" > if ! $CAT $Packages | grep -q "^Package:.*-$KVER-di" ; then > # show error message > # exit > fi > $CAT "$Packages" >> "$1" > > I'm guessing that for all architectures there will be at least one udeb that > has the kernel version in it. If not, the message could be a warning instead > of an error. > > The message could be something like: > It seems there are no installer components available that correspond to the > kernel version the Debian Installer was booted with. Please check you that > are using a correct mirror and a distribution that supports kernel version > $KVER. > > Is implementing this in net-retriever enough? Or should cdrom/floppy-retriever > do the same?
I've thought before about adding a check like that to anna. -- see shy jo
signature.asc
Description: Digital signature
