From: Jason <unleet@qwest.net>
To: speakup@braille.uwo.ca
Subject: Re: image file?
Date: Fri, 23 Nov 2001 21:59:24 -0700 [thread overview]
Message-ID: <01112321592400.02595@lightstar> (raw)
In-Reply-To: <5.1.0.14.2.20011123200439.00b14640@mail.buckeye-express.com>
simple, you need to put the new kernel image in the same place the old one
was.
basically, you just copy the bzImage file from
<path_to_kernel_source>/arch/i386/boot/bzImage to wherever your distribution
keeps the kernel image, then re-run lilo.
On Friday November 23, 2001 09:39 pm, you wrote:
> Hi all. Got a kernel compiling question for whoever can answer it. I
> downloaded the 2.4.15 kernel today and compiled it using the make mrproper,
> make menuconfig, make dep, make bzImage and make install procedure. I am
> running debian, and after running lilo at the end of the make install, I
> reboot the computer and the new kernel is not there. It is still reporting
> 2.2.18. Any suggestions on how to get my new kernel to come up?
>
> Thanks,
>
>
> Guy
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Glenn Ervin
` Gregory Nowak
` Georgina
` Guy Schlosser
` Jason [this message]
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=01112321592400.02595@lightstar \
--to=unleet@qwest.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).