From: "prince" <prince@resoftcorp.com>
To: netfilter@lists.netfilter.org
Subject: Re: How do I boot from different kernel when I don't have access to the console?
Date: Tue, 20 Jan 2004 22:03:04 -0800 [thread overview]
Message-ID: <20040121060304.M84032@resoftcorp.com> (raw)
In-Reply-To: <20040120045925.719da9c8.arnt@c2i.net>
Thank you Arnt and Ted,
It is very helpful.
Prince.
On Tue, 20 Jan 2004 04:59:25 +0100, Arnt Karlsen wrote
> 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.
next prev parent reply other threads:[~2004-01-21 6:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 9:22 kernel 2.6.x and iptables Muhammad Talha
2004-01-13 10:03 ` Unknown, Alistair Tonner
[not found] ` <200401130503.39528.Alistair Tonner <>
2004-01-13 10:24 ` Sven Schuster
2004-01-13 11:53 ` Muhammad Talha
2004-01-13 12:11 ` Muhammad Talha
2004-01-13 13:38 ` Unknown, Alistair Tonner
[not found] ` <200401130838.47327.Alistair Tonner <>
2004-01-13 15:33 ` Muhammad Talha
2004-01-13 21:15 ` Joel Newkirk
2004-01-14 5:30 ` Muhammad Talha
2004-01-14 20:08 ` How do I boot from different kernel when I don't have access to the console? prince
2004-01-14 20:14 ` prince
2004-01-19 23:40 ` Ted Kaczmarek
2004-01-20 3:59 ` Arnt Karlsen
2004-01-21 6:03 ` prince [this message]
2004-01-22 19:02 ` Ranjeet Shetye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040121060304.M84032@resoftcorp.com \
--to=prince@resoftcorp.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox