Your default=0, that will always boot the 2.4.20-28.9BOOT, change it to 1 and it will boot the other version. You can also pick the other one manually, but your timeout is only 10 seconds so pay attention :-) when booting. Ted On Wed, 2004-01-14 at 15:14, prince wrote: > Just to let you know, This is my /etc/grub.conf > > % sudo cat /etc/grub.conf > > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/hda3 > # initrd /initrd-version.img > #boot=/dev/sda > ### BEGIN AUTOMAGIC KERNELS LIST > default=0 > timeout=10 > splashimage=(hd0,0)/grub/splash.xpm.gz > > title Red Hat Linux (2.4.20-28.9BOOT) > root (hd0,0) > kernel /vmlinuz-2.4.20-28.9BOOT ro root=/dev/sda3 > initrd /initrd-2.4.20-28.9BOOT.img > title Red Hat Linux (2.4.20-28.9) > root (hd0,0) > kernel /vmlinuz-2.4.20-28.9 ro root=/dev/sda3 > initrd /initrd-2.4.20-28.9.img > ============================================================================= > On Wed, 14 Jan 2004 12:08:51 -0800, prince wrote > > Recently I downloaded some kernel*.rpm (Linux i386) from > > https://rhn.redhat.com/errata/RHSA-2003-417.html and I installed > > all the rpms using "rpm -iUvh kernel*.rpm". My mistake. I should > > have used "rpm - Fvh". Now I do not know what kernel was there > > previously. From the following output it looks, I had 2.4.20-18.9smp > > earlier. > > > > % ls -l /lib/modules/ > > total 12 > > drwxr-xr-x 3 root root 4096 Jan 6 15:03 2.4.20- > > 18.9smp drwxr-xr-x 3 root root 4096 Jan 12 16:01 > > 2.4.20-28.9 drwxr-xr-x 3 root root 4096 Jan 6 15:02 > > 2.4.20-28.9BOOT > > > > % rpm -qa | grep kernel > > kernel-pcmcia-cs-3.1.31-13 > > kernel-2.4.20-28.9 > > kernel-BOOT-2.4.20-28.9 > > kernel-doc-2.4.20-28.9 > > kernel-source-2.4.20-28.9 > > > > Now, whenever I boot the system it comes up with "2.4.20-28.9BOOT" > > which doesn't have iptables module. > > > > % lsmod > > Password: > > Module Size Used by Not tainted > > e1000 54528 1 > > ext3 61280 2 > > jbd 46804 2 [ext3] > > 3w-xxxx 36192 3 > > sd_mod 11916 6 > > scsi_mod 63416 2 [3w-xxxx sd_mod] > > > > % uname -a > > > > Linux dev9.my-comp.com 2.4.20-28.9BOOT #1 Thu Dec 18 13:27:13 EST > > 2003 i686 i686 i386 GNU/Linux > > > > I have ip tables in 2.4.20-28.9 > > % ls -l /lib/modules/2.4.20-28.9/kernel/net/ > > total 68 > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 8021q > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 appletalk > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 atm > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 ax25 > > drwxr-xr-x 4 root root 4096 Jan 6 15:02 bluetooth > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 bridge > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 decnet > > drwxr-xr-x 3 root root 4096 Jan 6 15:02 ipv4 > > drwxr-xr-x 3 root root 4096 Jan 6 15:02 ipv6 > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 ipx > > drwxr-xr-x 5 root root 4096 Jan 6 15:02 irda > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 netrom > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 rose > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 sched > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 sunrpc > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 tux > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 wanrouter > > > > /lib/modules/2.4.20-28.9/kernel/net/ipv4/netfilter/ip_tables.o > > > > But not under 2.4.20-28.9BOOT/ (there is no ipv?) > > % ls -l /lib/modules/2.4.20-28.9BOOT/kernel/net/ > > total 24 > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 8021q > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 ax25 > > drwxr-xr-x 4 root root 4096 Jan 6 15:02 bluetooth > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 netrom > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 rose > > drwxr-xr-x 2 root root 4096 Jan 6 15:02 sunrpc > > > > Now, I only have remote access to this server and I don't have > > access to the console at this time. > > > > Is there a way, I can boot the system with "2.4.20-28.9" instead of > > "2.4.20- > > 28.9BOOT". If the system does not come up properly, I should be able > > to reboot with "2.4.20-28.9BOOT" which is working (but no iptables). > > I have only remote power cycle capability. > > > > Could you please suggest a way to get this done? > > > > Note: This is follow-up to the question I earlier posted on > > "iptables v1.2.7a: can't initialize iptables table `filter':" > > > > thanks, > > Prince. > > > > >
