From: Steven Lembark <lembark@wrkhors.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] When did bzImage move?
Date: Thu, 05 Feb 2009 04:59:24 -0500 [thread overview]
Message-ID: <498AB87C.9080007@wrkhors.com> (raw)
In-Reply-To: <4985186C.2040001@gmail.com>
> But that would only allow you to have two kernels laying around. Right
> now I have these:
>
> root@smoker / # ls /boot/bzImage-2*
> -rw-r--r-- 1 root root 2355440 Jan 31 18:52 /boot/bzImage-2-28-r8-1
> -rw-r--r-- 1 root root 2460088 Jan 2 20:13 /boot/bzImage-2.6.23-r8-7
> -rw-r--r-- 1 root root 2288336 Dec 30 07:49 /boot/bzImage-2.6.27-r7-1
In the general config you can add a suffix. I
use a two-letter extension that goes up with each
installed version on the specific machine (never
reached past 26**2 but I could go to three letters).
That leaves you with bzImage-2.6.27.aa, bzImage-2.6.27.ab,
bzImage-2.6.28.ac, etc. At that point you can either put
them all into your menu.lst or just hack the command line
in grub to get an older kernel.
Q: How often do you really need to go back more than one
kernel?
If you have one especially clean, stable kernel for
disaster recovery just name it "stable" and have
two hard-wired entries for the vmlinuz and 'stable'.
--
Steven Lembark 85-09 90th St.
Workhorse Computing Woodhaven, NY, 11421
lembark@wrkhors.com +1 888 359 3508
next prev parent reply other threads:[~2009-02-05 9:59 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 2:41 [gentoo-user] When did bzImage move? Dale
2009-02-01 2:47 ` Volker Armin Hemmann
2009-02-01 2:57 ` Dale
2009-02-01 3:02 ` Volker Armin Hemmann
2009-02-01 3:35 ` Dale
2009-02-01 3:42 ` Volker Armin Hemmann
2009-02-01 4:38 ` [gentoo-user] " ABCD
2009-02-01 15:48 ` Neil Bothwick
2009-02-01 16:22 ` Geralt
2009-02-01 16:26 ` Volker Armin Hemmann
2009-02-01 16:46 ` Norberto Bensa
2009-02-01 16:50 ` Volker Armin Hemmann
2009-02-01 16:51 ` Dirk Heinrichs
2009-02-01 17:14 ` Geralt
2009-02-01 17:27 ` Tom
2009-02-01 17:34 ` Volker Armin Hemmann
2009-02-01 17:42 ` Neil Bothwick
2009-02-01 17:45 ` Jesús Guerrero
2009-02-01 18:37 ` Saphirus Sage
2009-02-02 4:53 ` Grant Edwards
2009-02-02 7:42 ` Dirk Heinrichs
2009-02-01 18:31 ` Harry Putnam
2009-02-01 19:11 ` Neil Bothwick
2009-02-02 15:22 ` Harry Putnam
2009-02-02 16:50 ` Tom
2009-02-02 23:28 ` [gentoo-user] localversion [was: When did bzImage move? ] David Relson
2009-02-02 23:37 ` [gentoo-user] Re: When did bzImage move? Neil Bothwick
2009-02-01 5:29 ` Nikos Chantziaras
2009-02-05 9:59 ` Steven Lembark [this message]
2009-02-05 10:02 ` [gentoo-user] " Dale
2009-02-01 21:32 ` KH
2009-02-01 21:37 ` Mark Knecht
2009-02-01 21:40 ` KH
2009-02-02 1:17 ` Tom
2009-02-01 22:03 ` Dale
2009-02-01 23:08 ` Mark Knecht
2009-02-01 23:27 ` Dale
2009-02-02 15:45 ` [gentoo-user] " Harry Putnam
2009-02-02 17:11 ` Dale
2009-02-02 1:05 ` [gentoo-user] " Neil Bothwick
2009-02-02 3:23 ` Stroller
2009-02-02 3:40 ` [gentoo-user] " »Q«
2009-02-02 3:46 ` [gentoo-user] " Dale
2009-02-02 4:25 ` Stroller
2009-02-02 4:57 ` Dale
2009-02-02 7:24 ` [gentoo-user] " ABCD
2009-02-02 9:45 ` [gentoo-user] " Neil Bothwick
2009-02-02 14:27 ` Mike Kazantsev
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=498AB87C.9080007@wrkhors.com \
--to=lembark@wrkhors.com \
--cc=gentoo-user@lists.gentoo.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