mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: kaos@ocs.com.au (Keith Owens)
Cc: linux-kernel@vger.kernel.org, kaih@khms.westfalen.de
Subject: Re: is 2.4.15 really available at www.kernel.org?
Date: Sat, 24 Nov 2001 14:56:18 +0100	[thread overview]
Message-ID: <200111241356.fAODuIb30257@ns.caldera.de> (raw)
In-Reply-To: <2450.1006608941@ocs3.intra.ocs.com.au>

In article <2450.1006608941@ocs3.intra.ocs.com.au> you wrote:
> kbuild 2.5 has standard support for running user specific install
> scripts after installing the bootable kernel and modules.  That is, the
> "update my bootloader" phase can be automated and will propagate from
> one .config to the next when you make oldconfig.

Never 2.4 kernels already try to excecute ~/bin/installkernel in the
'make install' pass on i386.

My personal tip for people keeping lots of kernels around is grub, though.
No need for a menu entry, one can just boot all kernel on the accessible
filesystems.

Together with the above "~/bin/installkernel" option I put my kernels always
into /lib/modules/<version>/vmlinux so I can find them easily (IMHO this
should be default in 2.5), so even lilo-using people could write simple
scripts to add all kernels present in /lib/modules/ to their config.
This does of course make the path '/lib/modules/' grossly misnamed, maybe
we could change it into /kernel in 2.5 :)

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  reply	other threads:[~2001-11-24 13:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23  8:58 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
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 [this message]
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=200111241356.fAODuIb30257@ns.caldera.de \
    --to=hch@ns.caldera.de \
    --cc=kaih@khms.westfalen.de \
    --cc=kaos@ocs.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®