From: Mike Fedyk <mfedyk@matchmail.com>
To: Flavio Stanchina <flavio.stanchina@tin.it>, linux-kernel@vger.kernel.org
Subject: Re: is 2.4.15 really available at www.kernel.org?
Date: Fri, 23 Nov 2001 13:08:20 -0800 [thread overview]
Message-ID: <20011123130820.D17332@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20212.1006507727@ocs3.intra.ocs.com.au> <Pine.LNX.4.33.0111230437180.7283-100000@localhost.localdomain> <20011123094313.GB190@tolot.miese-zwerge.org> <20011123103338.BXVP10632.fep40-svc.tin.it@there> <20011123110505.A27707@alcove.wittsend.com>
In-Reply-To: <20011123110505.A27707@alcove.wittsend.com>
On Fri, Nov 23, 2001 at 11:05:05AM -0500, Michael H. Warfield wrote:
> On Fri, Nov 23, 2001 at 11:33:38AM +0100, Flavio Stanchina wrote:
> > On Friday 23 November 2001 10:43, Jochen Striepe wrote:
> >
> > > I am *much* more irritated by:
> > >
> > > $ uname -r
> > > 2.4.15-greased-turkey
>
> > So I guess you are vegetarian. Try changing to "2.4.15-tasteful-salad".
>
> Point is that it BROKE some things.... Like "make install" on
> RedHat installed the damn thing as /boot/vmlinuz-2.4.15-greased-turkey,
> breaking the lilo settings if you set an image for "vmlinuz-2.4.15"
> like you expected it to be. Not funny. Just had three freeswan
> kinstall builds blow up because of that.
>
> Now got to go back and fix it and rebuild.
OMFG!
How can you *not* point to the /boot/vmlinuz symlink?!!! It points directly
to the latest kernel. And, /boot/vmlinuz.old points to the previous kernel.
Here are some examples: This is *just too simple*!!!
Lilo:
image=/boot/vmlinuz
label=vmlinuz
read-only
# restricted
alias=1
image=/boot/vmlinuz.old
label=vmlinuz-old
read-only
optional
append="single"
# restricted
alias=3
Grub:
title Debian GNU/Linux, Latest Kernel
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro vga=extended
title Debian GNU/Linux, Latest Kernel (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro single vga=extended
title Debian GNU/Linux, Previous Kernel
root (hd0,0)
kernel /boot/vmlinuz.old root=/dev/hda1 ro vga=extended
title Debian GNU/Linux, Previous Kernel (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz.old root=/dev/hda1 ro single vga=extended
next prev parent reply other threads:[~2001-11-23 21:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 8:58 is 2.4.15 really available at www.kernel.org? rpjday
2001-11-23 9:28 ` Keith Owens
2001-11-23 9:41 ` rpjday
2001-11-23 9:43 ` Jochen Striepe
2001-11-23 9:48 ` Rik van Riel
2001-11-23 10:00 ` Oliver.Neukum
2001-11-25 0:41 ` Cameron Simpson
2001-11-23 10:33 ` Flavio Stanchina
2001-11-23 16:05 ` Michael H. Warfield
2001-11-23 16:27 ` Jeff Garzik
2001-11-23 17:25 ` Michael H. Warfield
2001-11-23 19:19 ` Stephen Frost
2001-11-23 20:00 ` J Sloan
2001-11-23 21:08 ` Mike Fedyk [this message]
2001-11-23 23:54 ` Michael H. Warfield
2001-11-24 10:01 ` Kai Henningsen
2001-11-24 13:35 ` Keith Owens
2001-11-24 13:56 ` Christoph Hellwig
2001-11-24 22:29 ` H. Peter Anvin
2001-11-24 23:57 ` Keith Owens
2001-11-25 9:59 ` Kai Henningsen
2001-11-25 10:15 ` Mike Fedyk
2001-11-23 9:46 ` Christian Haugan Toldnes
2001-11-23 10:27 ` rpjday
2001-11-23 12:32 ` Stefan Smietanowski
2001-11-23 13:30 ` rpjday
2001-11-23 15:51 ` kees
2001-11-23 16:37 ` Michael H. Warfield
2001-11-23 20:10 ` Ross Vandegrift
2001-11-24 1:14 ` H. Peter Anvin
2001-11-23 20:28 ` Kristofer T. Karas
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=20011123130820.D17332@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=flavio.stanchina@tin.it \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.