I 'nuked' my /boot/vmlinuz

[arthurking]

I've never booted into it ever, but Lilo says that its missing.

 

Quick long story;

I mucked about with some 2.6.x kernels with mdk9.2.

I then updated to mdk10rc1.

B4 mdk10, Grub somehow managed to find a spot on my box?

Things were going well (they still are).

Then Lilo KO'ed Grub, I guess with the mdk10 upgrade.

I eventually rid my box of that old 2.4.x kernel to keep potentially hazardous thermo-nuclear reactions to a minimum

But.

vmliunz and initrd.img are links to the unwanted 2.4.22-28 kernel.

They exist only in name in the /boot dir. Both have 0 B file sizes.

If I run lilo to set my new favourite 2.6.x pet, as default (I'm as whimsical as I am frivolous), I get this terribly erroneous error that says vmlinuz doesn't exist.

So what!!!! I don't want to boot to vmlinuz, I want 2.6.3-4.

I thought that this vmlinuz was going to point to my mdk10 kernel.

But I was dellusional. Maybe the smoke coming from within the box while it was running the 2.4.x kernels affected my senses, common and all.

Well, that was the short story...

Q. Can I safely delete this /boot/vmlinuz, that I've never booted into, or will anti-matter come spewing out of the box next time I reboot it?

ps. I hate when anti-matter spews out. Didn't it create a universe or something last time that happened?

 

I followed some misguiding instructions to 'make clean' but this only served to 'make nothing' or 'make worse'

 

thanks for your replies, even if you don't.

[nggalai]

vmlinuz is just the "virtual" name of the kernel, in this case "the last thingy installed". If you nuked that one, just do a new softlink to the actual kernel (usually called vmlinuz-2.6.3blablablablamdk or whatever), and try again.

 

93,

-Sascha.rb

[arthurking]

Ah Ha!!

I kind of knew this fact. Virtual link thingy to last kernel installed.

I say, "kind of", because every other kernel install would change this link to the kernel I just installed.

But the vmlinuz that I currently have is pointing its linking(-ness)(-less?) to the old 2.4.22-28 kernel that I thought I deleted (obviously not).

 

Now you threw the soft link thingy in there too. WOAAHH!! (when I say woah.. I mean woah)

I never really realised that there were hard or soft links.

I remember doing a -ln to something somewhere a long time ago.

I can't remember how, although some reading of some stuff should help here.

 

But one question remains. Can I rm the vmlinuz or is there some boot process that requires it to be there even though it really isn't.

 

And my initrd.img follows the same line of questioning here. i.e. same problem, same question.

I also noticed just now, I somehow got 2.4.22-26mdksecure installed too!!

secure???!!! From what? Obviously not from my incompetence.

I don't remember asking to be secured :D

 

I just thought of something!

I'll rename it or something and re-boot.

 

C-ya.

and thanks.

[arthurking]

Renaming it to aavmlinuz didn't affect my ability to boot up :D

so I deleted the failsafe entry in lilo linking to vmlinuz and deleted /boot/vmlinuz and all is OK.

Phew!

Now I can easy

In fact the whole computer seems faster and less smoky

 

thanks for all the replies and non-replies. :D

 

done.

cheers.