From: James Miller <jamtat@mailsnare.net>
To: "EXT-Reimer, Jim D" <jim.d.reimer@boeing.com>
Cc: linux-newbie@vger.kernel.org
Subject: RE: 2.6.0 kernel compile overview
Date: Mon, 5 Jan 2004 14:09:46 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.58.0401051408430.3345@localhost> (raw)
In-Reply-To: <3DD6433F08A5A145AD7DA03566BDBFAF9F18DC@xch-sw-06.sw.nos.boeing.com>
On Mon, 5 Jan 2004, EXT-Reimer, Jim D wrote:
> >
> > I can't find the reference right now, but I think step 3
> > should actually be 'make install' if you want to get a
> > compressed kernel image and System.map file moved to either /
> > or /boot (if you have edited the Makefile to install to
> > /boot). If I am wrong, someone please correct me.
> >
>
> Here's an "overviewish" page covering the process:
> http://kerneltrap.org/node/view/799
>
Great link - thanks for providing it. It's got just about all I need to
proceed with this.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-01-05 20:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 19:39 2.6.0 kernel compile overview EXT-Reimer, Jim D
2004-01-05 20:09 ` James Miller [this message]
2004-01-05 22:08 ` 2.6.0 kernel compile overview-the unfolding saga James Miller
2004-01-05 22:19 ` caszonyi
2004-01-05 22:49 ` James Miller
2004-01-05 23:12 ` caszonyi
2004-01-06 6:05 ` Theo. Sean Schulze
2004-01-06 14:42 ` James Miller
2004-01-06 20:56 ` caszonyi
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 21:45 2.6.0 kernel compile overview chakkerz
2004-01-05 15:13 James Miller
2004-01-05 15:43 ` James Miller
2004-01-05 17:21 ` joy
2004-01-05 18:16 ` Theo. Sean Schulze
2004-01-05 21:36 ` James Turnbull
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=Pine.LNX.4.58.0401051408430.3345@localhost \
--to=jamtat@mailsnare.net \
--cc=jim.d.reimer@boeing.com \
--cc=linux-newbie@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