From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arnt Karlsen <arnt@c2i.net>
Subject: Re: How do I boot from different kernel when I don't have access	to
 the console?
Date: Tue, 20 Jan 2004 04:59:25 +0100
Sender: netfilter-admin@lists.netfilter.org
Message-ID: <20040120045925.719da9c8.arnt@c2i.net>
References: <00cb01c3d9b6$cd9b2d00$23c051cb@ns3.worldcall.net.pk>
	<008401c3d9cb$d634aa30$23c051cb@ns3.worldcall.net.pk>
	<00c201c3d9ce$62968d70$23c051cb@ns3.worldcall.net.pk>
	<012001c3d9ea$a64d8a20$23c051cb@ns3.worldcall.net.pk>
	<1074028552.1586.17.camel@alpha.newkirk.us>
	<00a801c3da5f$891ec7f0$23c051cb@ns3.worldcall.net.pk>
	<20040114200851.M90054@resoftcorp.com>
	<20040114201431.M65090@resoftcorp.com>
	<1074555651.20675.2.camel@tarkus>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <netfilter-admin@lists.netfilter.org>
In-Reply-To: <1074555651.20675.2.camel@tarkus>
Errors-To: netfilter-admin@lists.netfilter.org
List-Help: <mailto:netfilter-request@lists.netfilter.org?subject=help>
List-Post: <mailto:netfilter@lists.netfilter.org>
List-Subscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=subscribe>
List-Id: <netfilter.vger.kernel.org>
List-Unsubscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=unsubscribe>
List-Archive: <https://lists.netfilter.org/pipermail/netfilter/>
Content-Type: text/plain; charset="us-ascii"
To: netfilter@lists.netfilter.org

On Mon, 19 Jan 2004 18:40:52 -0500, 
Ted Kaczmarek <tedkaz@optonline.net> wrote in message 
<1074555651.20675.2.camel@tarkus>:

> 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

..also put in "fallback=0" below your new "default=1". 

> > 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

..behind your "root=/dev/sda3", append " panic=20 ", to avoid kernel
panics play USS Yorktown on your box.  ;-)

> 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.

..not 10 tenths of a second?  ;-)

..and it is also possible to set up serial consoles on modems or 
between remote boxes and have the paralell port control relays 
for power switches, before resorting to ups control tricks.  ;-)

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.