On Thursday 10 July 2003 00:37, Andreas Janssen wrote: > Hello > > cr wrote: > > However, I can't find anything on the CD-ROM called > > vmlinuz-2.2.20-idepci > > (which is the kernel in /boot that GRUB calls), or vmlinuz-2.2.20-***** > > > > I note also that /boot/vmlinuz-2.2.20-idepci and > > /cdrom/dists/woody/main/disks-i386/current/idepci/linux.bin > > are both 665509 bytes. > > > > So, is the vmlinuz kernel just the /idepci/linux.bin file copied and > > renamed? > > If I just do the same with .../current/linux.bin and rename it > > appropriately (and adjust Grub's menu.lst file) will it work? > > (More importantly, if it doesn't, will it break things? ) > > You should not try to replace your Kernel but to install another one in > case the new Kernel does not work.
Yes, that had occurred to me <grin> > Also, you need the kernel image file > and the modules. Instead of trying do do that manually, use apt-get. > You can use apt-get to intall Kernels (apt-cache search kernel-image, > apt-get install kernel-image...). I don't know about grub, but if you use > lilo, the package management system asks you if you want your bootloader > reconfigured automatically, this probably also works for grub. > > best regards > Andreas Janssen It looks as if the kernels on the Woody CD-ROMS aren't actually in the form of packages, since 'apt-cache search vanilla' (or compact, or idepci) brings up lists of other programs but nothing kernel-like. apt-cache search vmlinuz does nothing, nor apt-cache search linux.bin. I just found the 2.2.20 kernel package at www.debian.org and downloaded it (36 minutes on a 28k modem) and installed it with Kpackage (I'm lazy!), and it seems to be working. Aside from briefly breaking GRUB and having to fix it yet again because I got the /boot directories mixed up :) Further investigations will have to wait till later - after midnight now and I do have a day job <grin> Thanks Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
