public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@idb.hist.no>
To: John Nilsson <pzycrow@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Some experience of linux on a Laptop
Date: Mon, 25 Jun 2001 11:04:25 +0200	[thread overview]
Message-ID: <3B36FE99.1B8AE381@idb.hist.no> (raw)
In-Reply-To: <F175UFyfL1QMaCAP6Ki00001f92@hotmail.com>

John Nilsson wrote:
[everything else answered by others]

> 8: A way to change kernel without rebooting. I have no diskdrive or cddrive
> in my laptop so I often do drastic things when I install a new distribution.

Well, don't do drastic things then, if that cause problems!

My machines have both diskette and cdrom - but I _don't_ use them when
changing 
kernels.  Why should you?  Here is a procedure for painless kernel
change.
It includes a reboot but that is not a problem:

1. Get the new kernel, i.e. compile it.
2. cp the bzImage to /boot (or wherever you want it.)  DON'T overwrite
   the previous kernel image, you will want to keep it around.
3. If using lilo, modify /etc/lilo.conf to load the new kernel.
   Do this by _adding_ image=/boot/new_kernel_bzimage, not by changing
   existing lines.  This keeps the old kernel around in case the new
   one have trouble.
4. run lilo
5. reboot.

The new kernel should come up.  (If the old comes up you either
forgot (4), or you have the lilo.conf entries in a wrong order.
Int the latter case press shift furing boot and select the
correct kernel manually.  You may correct lilo.conf later.

If the new kernel loads but crash, do reboot and use the above
mentioned shift-trick to select the old kernel.  Then remove
the broken kernel from lilo.conf and re-run lilo.  

As you see, no need for CD's or floppies when changing kernels,
even if the new kernel fails somehow.

Helge Hafting

  parent reply	other threads:[~2001-06-25  9:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-24 20:51 Some experience of linux on a Laptop John Nilsson
2001-06-24 20:35 ` David Lang
2001-06-25  3:48   ` Eric W. Biederman
2001-06-25  6:09     ` David Lang
2001-06-25  8:38       ` Eric W. Biederman
2001-06-24 21:08 ` Fabian Arias
2001-06-24 21:22 ` Android
2001-06-24 21:22   ` Andrzej Krzysztofowicz
2001-06-25 17:47   ` Joseph Pingenot
2001-06-24 21:48 ` Alan Cox
2001-06-24 22:11   ` Jeff Chua
2001-06-24 22:15     ` Alan Cox
2001-06-24 22:11   ` William Stearns
2001-06-24 22:38   ` Hua Zhong
2001-06-25  3:45   ` Eric W. Biederman
2001-06-24 21:57 ` Daniel Phillips
2001-06-24 22:12   ` Alan Cox
2001-06-24 22:27     ` Daniel Phillips
2001-06-24 21:59 ` Rik van Riel
2001-06-24 22:26 ` Jeff Chua
2001-06-24 23:14 ` Luigi Genoni
2001-06-24 23:17 ` Keith Owens
2001-06-25  9:04 ` Helge Hafting [this message]
2001-06-25 10:09 ` PALFFY Daniel
2001-06-27  9:07 ` Julien Laganier
  -- strict thread matches above, loose matches on Subject: below --
2001-06-25  0:25 Dieter Nützel
2001-06-25  9:21 ` Luigi Genoni
2001-06-25 13:19 John Nilsson
     [not found] <fa.inojkfv.1tiu4gb@ifi.uio.no>
     [not found] ` <fa.gblj07v.1blumpa@ifi.uio.no>
2001-06-29 20:12   ` John Golubenko

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=3B36FE99.1B8AE381@idb.hist.no \
    --to=helgehaf@idb.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pzycrow@hotmail.com \
    /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