Re: lost /vmlinuz
do I need to create /vmlinuz and link to the kernel image (ln -s 2.2.15-idepci /vmlinuz)? you may do this, but this is not the way it should be done. Really? It's the way kernel-package does it ... aifak, the kernel creates /boot/vmlinuz, not /vmlinuz. however ... who cares? -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- If Windows is the answer, I want the problems back!
Re: lost /vmlinuz
Oswald Buddenhagen [EMAIL PROTECTED] wrote: do I need to create /vmlinuz and link to the kernel image (ln -s 2.2.15-idepci /vmlinuz)? you may do this, but this is not the way it should be done. Really? It's the way kernel-package does it ... aifak, the kernel creates /boot/vmlinuz, not /vmlinuz. Both, depending on how you look at it - it puts images into /boot/vmlinuz-* and links to them in /vmlinuz and /vmlinuz.old. I think RH uses /boot/vmlinuz as the link instead. however ... who cares? Well, quite :) -- Colin Watson [EMAIL PROTECTED]
lost /vmlinuz
I'm running potato on a pent 533EB and have been using 2.2.15-idepci , apt-get upgrade tried to upgrade my kernel image. I moved 2.2.15-idepci to .old and apt installed a new image but now when lilo tries to boot off the hard drive it complains that /vmlinuz is missing. In /lib/modules i've got 2.2.12, 2.2.15-idepci, 2.2.15-idepci.old do I need to create /vmlinuz and link to the kernel image (ln -s 2.2.15-idepci /vmlinuz)? I'm still able to get the system up by booting off the floppy, but, I'm lost beyond that. Thanks, Dave -- Debian GNU/Linux 2.2 100% M$ free
Re: lost /vmlinuz
do I need to create /vmlinuz and link to the kernel image (ln -s 2.2.15-idepci /vmlinuz)? you may do this, but this is not the way it should be done. you should reconfigure your /etc/lilo.conf (and run lilo afterwards). -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- If Windows is the answer, I want the problems back!
Re: lost /vmlinuz
apt-get upgrade tried to upgrade my kernel image. I moved 2.2.15-idepci to .old and apt installed a new image but now when lilo tries to boot off the hard drive it complains that /vmlinuz is missing. Yes, you've got exactly the idea -- recreate the vmlinuz symbolic link. As you've probably deduced, /vmlinuz is just a symbolic link pointing to the real kernel file which is located in /boot. As root, do the following: cd / (make sure we're in the root directory. rm vmlinuz (delete the old symbolic link because it's probably broken; we're going to recreate the symbolic link below anyway) ln -s boot/2.2.15-idepci vmlinuz (recreate the symbolic link; this of course will differ depending on what your kernel in /boot is named) liloconfig (run liloconfig so that lilo knows about the new kernel and can boot it) -- Regards, | The ultimate result is that some innovations that would .| truly benefit consumers never occur for the sole reason Randy| that they do not coincide with Microsoft's self-interest. | -- Judge Thomas Penfield Jackson, U.S. District Judge
Re: lost /vmlinuz
Thanks Randy, that worked perfectly! BTW, any idea as to what caused the problem to begin with? I got the 2.2.12 kernel when I dist-upgrade to potato, then the 2.2.15-idepci kernel by way of apt-get install kernel-image-2.2.15-idepci and when I ran apt-get upgrade last night the package mgmt didn't like the way I acquired 2.2.15-idepci :( apt-get upgrade tried to upgrade my kernel image. I moved 2.2.15-idepci to .old and apt installed a new image but now when lilo tries to boot off the hard drive it complains that /vmlinuz is missing. Yes, you've got exactly the idea -- recreate the vmlinuz symbolic link. As you've probably deduced, /vmlinuz is just a symbolic link pointing to the real kernel file which is located in /boot. As root, do the following: cd / (make sure we're in the root directory. rm vmlinuz (delete the old symbolic link because it's probably broken; we're going to recreate the symbolic link below anyway) ln -s boot/2.2.15-idepci vmlinuz (recreate the symbolic link; this of course will differ depending on what your kernel in /boot is named) liloconfig (run liloconfig so that lilo knows about the new kernel and can boot it) -- Regards, | The ultimate result is that some innovations that would .| truly benefit consumers never occur for the sole reason Randy| that they do not coincide with Microsoft's self-interest. | -- Judge Thomas Penfield Jackson, U.S. District Judge -- Debian GNU/Linux 2.2 100% M$ free
Re: lost /vmlinuz
Oswald Buddenhagen [EMAIL PROTECTED] wrote: do I need to create /vmlinuz and link to the kernel image (ln -s 2.2.15-idepci /vmlinuz)? you may do this, but this is not the way it should be done. Really? It's the way kernel-package does it ... -- Colin Watson [EMAIL PROTECTED]
