... /lib/modules has a directory called
2.6.10-mm3-250405
which contain...
lrwxrwxrwx 1 root root 21 Feb 25 09:22 build -> /usr/src/linux-2.6.10
drwxr-xr-x 7 root root 4096 Feb 25 09:22 kernel
-rw-r--r-- 1 root root 55050 Feb 25 09:22 modules.alias
-rw-r--r-- 1 root root 69 Feb 25 09:22 modules.ccwmap
-rw-r--r-- 1 root root 16342 Feb 25 09:22 modules.dep
-rw-r--r-- 1 root root 73 Feb 25 09:22 modules.ieee1394map
-rw-r--r-- 1 root root 205 Feb 25 09:22 modules.inputmap
-rw-r--r-- 1 root root 10168 Feb 25 09:22 modules.isapnpmap
-rw-r--r-- 1 root root 12839 Feb 25 09:22 modules.pcimap
-rw-r--r-- 1 root root 12618 Feb 25 09:22 modules.symbols
-rw-r--r-- 1 root root 145351 Feb 25 09:22 modules.usbmap
lrwxrwxrwx 1 root root 21 Feb 25 09:22 source -> /usr/src/linux-2.6.10

To tidy up from the package install..

remove the via-rhine & via module names from /etc/modules & /etc/modules/aliases as they are compiled in now..
and do update-modules

Do iptables-save to show any existing loaded rules

and set up another session to ping the boxes NIC
You can then watch it go down and come back up!!
Kind of the last torture before judgement day!!

Do you have linear in lilo.conf?

done
- now?.................

this has been a long thread - and it might not be over yet..... do you think this is what irc was invented for (might have been quicker!)

Ooops..

I've just killed your lilo...

The -l option forced LINEAR... BAD BAD BAD

Do lilo -v again pls

Then do lilo -R linux.new

Then it's safe to reboot...

no linear in lilo.conf: should there be?

typing:
lilo -v
gives me:
LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 17-Nov-2004, and compiled at 20:30:43 on Dec 9 2004
Debian GNU/Linux

Reading boot sector from /dev/hda
Using MENU secondary loader
Calling map_insert_data

Boot image: /boot/vmlinuz-2.4.18-bf2.4
Added Linux *

Boot image: /boot/vmlinuz-2.6.10-mm3-250405
Added linux.new

Writing boot sector.
/boot/boot.0300 exists - no boot sector backup copy made.

typing :
lilo -R linux.new
...nothing

OK 2 go now?............... (sound of held breath)

Ok
time to go now, if you have to... hehehe

Got the ping going??

hooray - it's back up! and with the right linux version

and iptables works!
well done!
i am going out for a beer now!
before i die of thirst.

thanx

Well done there!

That's a sarge boot without initrd or udev or devfs or sysfs..

....is there anything i need to do to get the system to boot to that image every time...

like modify lilo.conf (make linux.new the default) and run lilo again?

Yes, all those..

In lilo.conf, change the Default = line to say linux.new
then lilo -v to make it stick..

The only time you will need to reboot is to test the boot procedure, eg simulate mains fail, or changing kernels.
Because of the extra kernels etc in /boot, it would be a good time to remove any files not related to linux.new or the last kernel, including the /lib/modules directories of the unrelated kernels..
Keep the sources! In fact make a copy of the entire directory exactly as it is now.
Make the directory name of the original sources match the Makefile version number.

There will be a few modifications to recommend once you get to running as a backup server, but they should be different threads...
Congratulations..

OK - changed linux.new to the default in lilo.conf & ran lilo... rebooted everything huncky-dory..... have now set up a nice simple firewall and can get on with what i bought the thing for!

Thanks for your help Peter (what a nice man!)